# changes Published articles for changes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## GNOME 51 released DevFeed: [GNOME 51 released]() Original publisher: [Read original article]() Author: corbet Published: 2026-09-17T13:08:12Z Content type: release Language: en Sources: [LWN.net]() Topics: [version](), [App](), [data](), [interface](), [file]() Tags: [application](), [changes](), [data](), [desktop](), [file](), [gnome](), [gnome-51](), [improvements](), [interface](), [maps](), [offline](), [performance](), [transit](), [version]() ### AI overview GNOME 51 has been released with performance improvements, offline data and improved transit information in Maps, a new file previewer interface, and other changes. ### Source excerpt Version 51 of the GNOME desktop environment has been released. The list of changes includes a number of performance improvements, offline data and better transit information in the Maps application, a new interface for the file previewer, and more. ## Libreboot 20150124 release DevFeed: [Libreboot 20150124 release]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [Hardware](), [boot]() Tags: [article](), [bios](), [canoeboot](), [changes](), [coreboot](), [free-software](), [grub](), [hardware](), [libre](), [libreboot](), [mac](), [opensource](), [release](), [thinkpad](), [uefi](), [update](), [usb]() ### AI overview Libreboot's 24 January 2015 release supports several Lenovo ThinkPad models and Apple MacBook models. It removes ME/AMT on supported Lenovo systems and includes updates to GRUB parsing, ARM binaries, Flashrom, X200 backlight handling, and utilities for changing MAC addresses and generating firmware images. ### Source excerpt Article: Libreboot 20150124 release Web link: https://libreboot.org/news/libreboot20150124.html ## New Bug-Fix Releases Are Available for MPS Versions 2026.1.1, 2025.3.2, 2025.2.4, and 2025.1.4 DevFeed: [New Bug-Fix Releases Are Available for MPS Versions 2026.1.1, 2025.3.2, 2025.2.4, and 2025.1.4]() Original publisher: [Read original article]() Author: Vaclav Pech Published: 2026-09-16T20:06:31Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [JetBrains MPS](), [releases](), [version](), [jetbrains]() Tags: [2](), [2025](), [2026](), [3](), [agent](), [agents](), [bug](), [changes](), [create](), [development](), [diagnostics](), [editor](), [improvements](), [major](), [manipulate](), [mps](), [practical](), [release](), [releases](), [updates](), [version]() ### AI overview JetBrains has released bug-fix updates for MPS versions 2026.1.1, 2025.3.2, 2025.2.4, and 2025.1.4. The MPS 2026.1.1 update includes improvements to the Projectional Agent Toolkit, editor context, diagnostics, agent guidance, and test execution. ### Source excerpt We've released updates for multiple major MPS versions that fix several issues. DOWNLOAD MPS 2026.1.1 Check out all the updates in each particular version below: MPS 2026.1.1 The Projectional Agent Toolkit receives several practical improvements that allow agents to: See and invoke intentions and quick-fixes on individual nodes. Manipulate NodeAttributes, PropertyAttributes, and others. Create copies [...] ## Observations From Building a PR Review Loop DevFeed: [Observations From Building a PR Review Loop]() Original publisher: [Read original article]() Author: Josh Sherman Published: 2026-08-02T00:00:00Z Content type: opinion Language: en Sources: [Josh Sherman]() Topics: [Pull Request](), [Code](), [Security](), [Git](), [forgejo]() Tags: [agent](), [changes](), [code](), [git](), [review](), [security]() ### AI overview The author describes building an agent-driven pull request review loop and the problems encountered when reviewing large changes. A diff-only reviewer repeatedly requested changes, contributing to review loops, while model changes were associated with a roughly halved approval rate. Security constraints intentionally prevent the reviewer from using command-line tools, so a separate worker agent verifies feedback against the working tree and attempts remediation. ### Source excerpt Building my own agent has been fun. Sure, I could have opted for an off-the-shelf solution, but I wanted control. The ironic part is that I'm using that control to offload more control to the agent. Recent experiments have included letting the agent work on itself. Super meta, but didn't quite go as planned considering the guardrails I have in place around the size of PRs. Agent work tends to be heavy lifting, whereas most project work is small and fits nicely inside the constraints. Part of the issue there is that the PR reviewer would constantly request changes on those larger PRs. Changes would happen, PR message body would diverge. Infinite loop death spiral until eventually I was called. Around this same time, I was also tracking some issues that started to creep in after I changed some models from Opus 4.8 to Opus 5. Approval rate dropped by about half. I like to think that each new model is going to be better than the last, so I thought perhaps it was time to revisit the reviewer to see if there was something we were missing. The review mechanic By design, the review persona is pretty dumb. Not dumb in the sense that I give it a lesser model or anything. Dumb in that it just doesn't have the full picture of things. It gets the PR diff as a blob of text and that's it. No git worktree, no way to read files or grep around. No commit messages or recent changes to compare against. I don't review PRs this way. I click around and look at adjacent code. I'll git checkout the branch locally and poke around. I try to gather as much as I can to give feedback with more substance than nit: stray line break or the like. Because of this, a lot of the feedback from the reviewer was effectively LGTM, but I can't really confirm anything so... lol good luck. Then I'd get pinged to take a closer look. Safety first It's probably not fair to say the reviewer is dumb. The reviewer is gated by security checks. I'm the only user on my personal Forgejo instance, but that doesn't mean ## OpenTelemetry Demo 3.0 introduces breaking changes to attributes, dashboards, and local deployment DevFeed: [OpenTelemetry Demo 3.0 introduces breaking changes to attributes, dashboards, and local deployment]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-28T10:15:19Z Content type: opinion Language: en Sources: [Blog on OpenTelemetry]() Topics: [Demo](), [OpenTelemetry](), [Maintainability](), [dashboards](), [Kafka]() Tags: [changes](), [dashboards](), [demo](), [maintainability](), [opentelemetry](), [services]() ### AI overview This article explains intentional breaking changes in OpenTelemetry Demo 3.0, including renamed custom telemetry attributes, broken dashboards and queries, and a revised local-run configuration split across multiple files. The changes aim to improve maintainability and make forks easier to manage. ### Source excerpt If you've been running the Demo for some time, you may have seen a couple of structural changes lately, and you may even have gotten mad about things not working as expected. We feel your pain and we totally understand it. Unfortunately there was no better way to change things without breaking the existing flow. Some of what you knew is gone. New services were added. Attribute names have changed. If you had dashboards with custom metrics, everything is broken now. ## Keycloak Client Libraries 26.0.11 released DevFeed: [Keycloak Client Libraries 26.0.11 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-07-15T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [client](), [servers](), [ci](), [migration]() Tags: [2026](), [bugs](), [changes](), [ci](), [client](), [idm](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [migration-guide](), [openid-connect](), [release](), [resolved](), [saml](), [sso]() ### AI overview Keycloak Client Libraries 26.0.11 was released on July 15, 2026. The release notes mention an enhancement to sync after the Keycloak server 26.7.0 release and a CI failure issue in keycloak-client. Users are directed to the migration guide before upgrading. ### Source excerpt Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #226 Sync after Keycloak server 26.7.0 release client Bugs #222 keycloak-client CI is failing client ## Keycloak Client Libraries 26.0.10 released DevFeed: [Keycloak Client Libraries 26.0.10 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [client](), [Keycloak](), [Documentation]() Tags: [bugs](), [changes](), [client](), [docs](), [guide](), [idm](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [openid-connect](), [resolved](), [saml](), [sso]() ### AI overview Keycloak Client Libraries 26.0.10 was released on June 30, 2026. The release includes resolved issues involving supported Keycloak server versions and downstream documentation builds. ### Source excerpt Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Bugs #208 Clarification of supported keycloak server versions client #210 Latest changes break downstream docs build for 26.6 client ## Optimizing LLVM's bump allocator DevFeed: [Optimizing LLVM's bump allocator]() Original publisher: [Read original article]() Published: 2026-06-28T07:00:00Z Content type: article Language: en Sources: [MaskRay]() Topics: [LLVM](), [clang]() Tags: [changes](), [clang](), [codegen](), [debug](), [llvm](), [memory](), [optimizing](), [performance]() ### AI overview This article explains three recent changes that optimize LLVM's BumpPtrAllocator: avoiding unnecessary realignment, using a sentinel to eliminate a null check, and removing per-allocation accounting from the hot path. It also discusses alignment, typed allocation, incomplete types, and ABI considerations. ### Source excerpt BumpPtrAllocator is LLVM's bump allocator (arena allocator): each allocation bumps a pointer within a slab, and everything is freed at once when the allocator dies. It backs Clang's ASTContext, lld's make object pools, TableGen records, and many other arenas. Here is the fast path before three recent changes: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 __attribute__((returns_nonnull)) void *Allocate(size_t Size, Align Alignment) { BytesAllocated += Size; // (3) accounting RMW uintptr_t AlignedPtr = alignAddr(CurPtr, Alignment); // (1) always realign size_t SizeToAllocate = Size; #if LLVM_ADDRESS_SANITIZER_BUILD SizeToAllocate += RedZoneSize; #endif uintptr_t AllocEndPtr = AlignedPtr + SizeToAllocate; if (LLVM_LIKELY(AllocEndPtr <= uintptr_t(End) && CurPtr != nullptr)) { // (2) bound + null check CurPtr = reinterpret_cast(AllocEndPtr); ... return reinterpret_cast(AlignedPtr); } return AllocateSlow(Size, SizeToAllocate, Alignment); } ## How Rain Affects Wireless Microwave Links: 24 GHz, 60 GHz, and 80 GHz Compared DevFeed: [How Rain Affects Wireless Microwave Links: 24 GHz, 60 GHz, and 80 GHz Compared]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-15T09:47:43Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Network](), [Network design](), [Internet](), [data centers]() Tags: [24ghz](), [60ghz](), [80ghz](), [adaptive](), [backhaul](), [capacity](), [changes](), [e-band](), [error-correction](), [fiber](), [microwave](), [network](), [network-design](), [perfomance](), [radio](), [reduction](), [rf](), [wireless](), [wireless-networking]() ### AI overview This article explains how rain fade affects wireless microwave links, with emphasis on 24 GHz, 60 GHz, and 80 GHz bands. It describes how precipitation reduces signal strength, causes adaptive modulation and throughput reductions, and can eventually cause a link to drop when fade margin is exhausted. ### Source excerpt Rain can have a major impact on wireless microwave links, especially as frequencies increase. Learn how rain fade affects 24 GHz, 60 GHz, and 80 GHz circuits, and why fade margin is critical for reliable network design. The post How Rain Affects Wireless Microwave Links: 24 GHz, 60 GHz, and 80 GHz Compared appeared first on Justin Wilson (j2sw). ## How AI Changes the Role of Applied Scientists DevFeed: [How AI Changes the Role of Applied Scientists]() Original publisher: [Read original article]() Author: Tilman Drerup Published: 2026-05-22T17:40:32Z Content type: article Language: en Sources: [Instacart]() Topics: [Artificial Intelligence](), [Data Science](), [AI, ML & Data Engineering]() Tags: [ai](), [analysis](), [applied-science](), [artificial-intelligence](), [changes](), [coding](), [economics](), [machine-learning](), [math](), [statistics]() ### AI overview Instacart's Economics Team examines how artificial intelligence is changing the work of applied scientists. The article frames the role as a bundle of tasks and proposes analyzing changes in the team's project portfolio from 2023 onward, with potentially larger effects on coding than on causal inference. ### Source excerpt Levi Boxell, Tilman Drerup, Alexandr Lenk The Economics Team at Instacart is an applied science team that operates at the intersection of machine learning engineering and economics. Similar to other applied science teams, our work involves a good chunk of engineering, steeped in statistics, math, theory, and strategy. And while that is still at the heart of what we do today, the surprisingly rapid emergence of artificial intelligence has also fundamentally altered our work in ways that we did not see coming. With this post, we want to provide a brief check-in and share an analysis of the patterns we are seeing from a distinctly economic perspective. To do so, we analyze the empirical dynamics of our project portfolio between 2023 and today, looking at the evolution of both the nature and quantity of our work over time. To start, let's have a quick refresher of what economists at Instacart do and provide a theoretical framework to think about the impact of technological change through AI. Background & Theoretical Framework At Instacart, economists spend their day-to-day on a diverse portfolio of tasks and activities. Similar to other applied science teams within the company, our work relies on a blend of skills, including economics, statistics, math, machine learning, data manipulation, coding, and AI. Due to this versatility in tasks, the team's work provides a particularly rich testing ground for predictions derived from economic theories concerning the impact of technological change. But what does economic theory actually tell us? A useful theoretical abstraction for an applied scientist's role is to frame it as a bundle of tasks (Autor, Levy, and Murnane, 2003), with each task characterized by its own production function (Acemoglu and Autor, 2011). Slightly simplified, a production function tells us how much output we can produce for a given level of input in a specific task. Comparisons of production functions across tasks in turn determine how we allocate our t ## Keycloak experimental AuthZEN Support DevFeed: [Keycloak experimental AuthZEN Support]() Original publisher: [Read original article]() Author: Ryan Emerson Published: 2026-05-20T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authorization](), [openid](), [API](), [REST API](), [interoperability](), [vendor lock-in]() Tags: [authentication](), [changes](), [idm](), [interoperability](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [release](), [resource](), [rest-api](), [saml](), [sdks](), [sso](), [vendor-lock-in](), [works]() ### AI overview Keycloak announces experimental support for the OpenID AuthZEN Authorization API 1.0 specification starting with version 26.7.0. The feature lets Keycloak act as a Policy Decision Point and expose existing authorization policies through a standardized API for Policy Enforcement Points. ### Source excerpt We are excited to announce that from 26.7.0, Keycloak will include experimental support for the OpenID AuthZEN Authorization API 1.0 specification. This allows Keycloak to act as a Policy Decision Point (PDP), exposing its authorization capabilities through a standardized API that any Policy Enforcement Point (PEP) can consume. You can try this now with the Keycloak nightly release. Why AuthZEN? Authorization has long been fragmented, with competing systems defining their own protocols for answering the same fundamental question: "Can this subject perform this action on this resource?". This means applications are tightly coupled to whichever authorization backend they choose, and swapping providers requires rewriting integration code. AuthZEN changes this by defining a single, vendor-neutral API between the component that asks (the PEP) and the component that decides (the PDP). It is, in many ways, what OpenID Connect did for authentication -- but for authorization. With AuthZEN: No more vendor lock-in -- your application speaks one API regardless of the PDP behind it. RBAC, ABAC, and ReBAC under one roof -- different policy models can answer the same request format, enabling true interoperability across authorization paradigms. Centralized, externalized authorization -- policy logic lives in the PDP, not scattered across application code, making it easier to audit and update. Simpler integration -- a clean REST API with a minimal request/response model replaces complex, implementation-specific SDKs. A growing ecosystem OpenID AuthZEN Interop demonstrates that over a dozen independently-developed PDPs can be used interchangeably by the same PEP without changing a single line of application code. By adding AuthZEN support, Keycloak joins this ecosystem and lets you leverage your existing Keycloak policies through the same standardized API used by every other AuthZEN-compatible PDP. How it works The interaction between your application and Keycloak follows the standard PE ## How Terraform Works DevFeed: [How Terraform Works]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-05-05T07:41:46Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Terraform](), [Infrastructure as code](), [Provisioning](), [CI/CD](), [Pull Request](), [Command-line interface]() Tags: [changes](), [ci-cd](), [hcl](), [infrastructure-as-code-iac](), [plan](), [preview](), [provisioning](), [terraform]() ### AI overview A step-by-step introduction to how Terraform uses Infrastructure as Code and HCL configurations to define resources, preview changes with Terraform Plan, and provision infrastructure with Terraform Apply. It also explains providers, variables, modules, state, workspaces, and CI/CD or pull-request workflows. ### Source excerpt Step by step ## How Agentic AI Creates Gaps in Audit-Trail Accountability DevFeed: [How Agentic AI Creates Gaps in Audit-Trail Accountability]() Original publisher: [Read original article]() Author: flashdba Published: 2026-04-27T13:43:04Z Content type: opinion Language: en Sources: [flashdba]() Topics: [AI Agent](), [audit trail](), [audit]() Tags: [account](), [agentic](), [agentic-ai](), [ai](), [ai-agent](), [audit](), [audit-trail](), [changes](), [cloud](), [commit](), [compliance](), [credentials](), [databases](), [databases-and-agentic-ai](), [identity](), [inferencing](), [model](), [performance](), [regulatory](), [service]() ### AI overview The article argues that conventional audit trails can record database changes accurately while failing to explain an AI agent's reasoning or establish accountable human ownership. It identifies unstable agent identity and the absence of externally documented reasoning as the central gaps. ### Source excerpt The audit trail still runs. Every commit is recorded. But agentic AI has broken the two assumptions it was built on - and the incompleteness is invisible until you need it. ## Keycloak JS 26.2.4 released DevFeed: [Keycloak JS 26.2.4 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-04-22T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Cordova](), [Authentication](), [browser](), [version]() Tags: [authentication](), [browser](), [bug-fixes](), [changes](), [cordova](), [idm](), [kerberos](), [keycloak](), [keycloak-js-release](), [ldap](), [openid-connect](), [saml](), [sso](), [version]() ### AI overview Keycloak JS 26.2.4 fixes two Cordova adapter regressions introduced in version 26.2.1. It prevents duplicate authentication requests during token exchange and closes the in-app browser before the exchange begins, avoiding a brief Android error. ### Source excerpt Highlights This release of Keycloak JS addresses two regressions in the Cordova adapter that were introduced in version 26.2.1. Bug Fixes Cordova adapter no longer triggers duplicate authentication requests A regression introduced in version 26.2.1 caused the Cordova in-app browser to fire multiple loadstart events before the token exchange completed, resulting in concurrent authentication requests that could fail the login flow. The completed flag is now set before awaiting the token exchange, preventing duplicate processing of the redirect URI. keycloak/keycloak-js#208 Cordova in-app browser now closes before awaiting token exchange A regression introduced in version 26.2.1 caused the Cordova in-app browser to remain open during the asynchronous token exchange, resulting in a brief "Web page not available" error flashing on Android before the browser eventually closed. The browser is now closed immediately after the redirect URI is captured, before the token exchange begins. keycloak/keycloak-js#209 Upgrading Before upgrading refer to the migration guide for a complete list of changes. ## AI agents are shipping faster than anyone can document DevFeed: [AI agents are shipping faster than anyone can document]() Original publisher: [Read original article]() Author: Hahnbee Lee Published: 2026-03-09T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Artificial Intelligence](), [Documentation](), [Software](), [Software as a service]() Tags: [agents](), [ai](), [ai-agents](), [announcements](), [automatically](), [changes](), [docs](), [documentation](), [product](), [updating]() ### AI overview The article argues that AI agents are advancing faster than teams can maintain their documentation. It presents Mintlify's Automations as a way to define triggers and instructions that automatically update documentation when a product changes, helping keep information current for AI-facing tools and customers. ### Source excerpt AI agents are shipping faster than anyone can document. Automations closes the gap by automatically updating your docs when your product changes. ## Metro 0.11.0 and MEEPs! DevFeed: [Metro 0.11.0 and MEEPs!]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-02-25T05:08:43Z Content type: release Language: en Sources: [Zac Sweers]() Topics: [Development](), [Kotlin]() Tags: [bugfixes](), [changes](), [community](), [development](), [interop](), [new-features]() ### AI overview Metro 0.11.0 has been released after a period focused on foundation, interop, and feature parity. The release introduces MEEPs, a proposal mechanism for planned features and community feedback, and includes three implemented MEEPs alongside bug fixes, improvements, promoted features, and behavior changes. ### Source excerpt Metro 0.11.0 is out now and it's a fun milestone in Metro's development. Up to this point most of the work in Metro has been focused around the foundation, interop, and frankly feature parity. It's in a really good place on that ## Review of the Self-Defining Systems proposal for AI-driven system development DevFeed: [Review of the Self-Defining Systems proposal for AI-driven system development]() Original publisher: [Read original article]() Author: Aleksey Charapko Published: 2026-01-30T01:24:00Z Content type: opinion Language: en Sources: [Aleksey Charapko]() Topics: [systems](), [Artificial Intelligence](), [Specifications](), [Processes]() Tags: [agentic](), [agents](), [ai](), [changes](), [improvements](), [llm](), [one-page-summary](), [papers](), [performance](), [research](), [specifications](), [systems]() ### AI overview The article reviews Self-Defining Systems, a proposal in which agentic engineers design and build systems from system and operating-environment specifications. It argues that the proposal extends the familiar try, evaluate, and repeat loop by allowing agents to change the specification as well as implement it, while noting that the paper lacks a precise definition of the process. ### Source excerpt Self-Defining Systems (SDS) by Thomas Anderson, Ratul Mahajan, Simon Peter, and Luke Zettlemoyer is a bold proposal for AI-driven systems research. In SDS, agentic "engineers" get the system specification and operating environment specification, then design and build the systems to spec. Crucially, as the specification or environment changes, an army of agents should notice and [...] ## Keycloak 26.4.4 released DevFeed: [Keycloak 26.4.4 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-11-07T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [version](), [OpenID connect (OIDC)](), [LDAP](), [Quarkus]() Tags: [changes](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [oidc](), [openid-connect](), [quarkus](), [release](), [saml](), [sso](), [version]() ### AI overview Keycloak 26.4.4 is released with enhancements and fixes covering client-scope discovery, verification-email rate limiting, workflow authorization, fine-grained permissions, OIDC, LDAP, WebAuthn, memory usage, and other administration and infrastructure issues. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #10388 Allow to hide client scopes from scopes_supported in discovery endpoint #43076 Add rate limiter for sending verification emails in context of update email #43509 Role authorization for workflows. admin/api Bugs #41270 Cannot save new attribute group admin/ui #41271 Changing user profile attribute results in an error everytime admin/ui #43082 ExternalLinksTest is broken due to missing path parameters docs #43091 Duplicate Email Fields on Temporarily Locked Out Sign In With Organization Identity-First Login login/ui #43160 Regression in DEBUG_PORT handling since 26.4.0 - host binding (*:port / 0.0.0.0:port) no longer works dist/quarkus #43460 FGAP/UI: `reset-password` succeeds but UI shows 403 without Users:manage admin/fine-grained-permissions #43505 DPoP proof replay check doesn't consider clock skew oidc #43516 Deleting Client is slow and fails when a lot of client sessions exist core #43578 "admin" client role now requires server admin user admin/api #43579 403 Forbidden when assigning realm-management client roles with realm-admin despite FGAP disabled (regression in 26.4.0+) admin/fine-grained-permissions #43596 FGAP: user can no longer open account management page, broken by `reset-password` admin/fine-grained-permissions #43621 Version 26.4.1 breaks existing ldap users with capital letters in username ldap #43682 When syncing roles, the database layer can see deadlocks #43698 Role Mapper is updating the user every time on login identity-brokering #43723 Only add the none verifier when attestation conveyance preference is none (or default) authentication/webauthn #43734 Refresh token allowed for offline session even the related scope is removed #43736 FGAP V2: reset-password scope error when viewing users with Group permissions only core #43744 Increased memory usage due to leaking Keyc ## Progress update: fixing the ReactOS test suite DevFeed: [Progress update: fixing the ReactOS test suite]() Original publisher: [Read original article]() Published: 2025-11-04T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [Testing](), [WINE](), [Windows](), [gcc](), [MSVC](), [x86]() Tags: [changes](), [developer](), [free](), [gcc](), [msvc](), [open-source](), [os](), [react](), [reactos](), [tests](), [update](), [win32](), [winapi](), [windows](), [wine](), [x86]() ### AI overview A ReactOS project developer describes work to clean up the neglected test suite. The update reports fixes to 55 existing test modules, five new modules, broader testing across Windows versions and compiler toolchains, and changes intended to improve synchronization with Wine 10.0. The supplied text also states that the full test suite can now run on Windows Vista without a bugcheck. ### Source excerpt For many years, the ReactOS test suite was neglected. It was a random collection of our own tests and old Wine tests that were only checked against Windows Server 2003 and sometimes a random newer version of Windows up to the discretion of the contributor. The Wine tests we imported were heavily modified and the changes made weren't always well documented. I'm here to clean up this mess. I have been deeply involved with the ReactOS project since 2023 and in May of 2024 I became an official project developer. ## Keycloak Client Libraries 26.0.7 released DevFeed: [Keycloak Client Libraries 26.0.7 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-10-01T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [client](), [Keycloak](), [servers]() Tags: [bugs](), [changes](), [client](), [idm](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [migration-guide](), [openid-connect](), [release](), [resolved](), [saml](), [server](), [sso]() ### AI overview Keycloak Client Libraries 26.0.7 was released on October 1, 2025. The release notes list enhancements, synchronization with the Keycloak server 26.4.0 release, and a bug involving EdECUtilsImpl in keycloak-client-common-synced. ### Source excerpt Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #176 Update RELEASE-CHECKLIST.md and README.md files client #187 Sync after Keycloak server 26.4.0 release client Bugs #184 EdECUtilsImpl is not included in keycloak-client-common-synced client ## Blog: Introducing Falco 0.41.0 DevFeed: [Blog: Introducing Falco 0.41.0]() Original publisher: [Read original article]() Published: 2025-05-29T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [eBPF](), [Kubernetes](), [configuration](), [container](), [JSON](), [Prometheus](), [bug](), [Code Modularity]() Tags: [bug-fixes](), [capabilities](), [changes](), [code-modularity](), [configuration](), [container](), [ebpf](), [falco](), [json](), [kubernetes](), [prometheus](), [release](), [ux]() ### AI overview Falco 0.41.0 introduces revised container engine support, an early Kubernetes operator, configurable merge strategies, expanded eBPF driver behavior, new field access options, and JSON output controls. The release also includes fixes for kernel-module crashes, Prometheus metrics, RPM scripts, and configuration overrides. ### Source excerpt Dear Falco Community, today we are happy to announce the release of Falco 0.41.0! This version brings several new features, performance enhancements, and bug fixes that streamline Falco's detection capabilities. During this release cycle, we merged more than 50 PRs on Falco and around 130 PRs for libs and drivers, version 0.21.0 and version 8.1.0, respectively. Thank you to our maintainers and contributors. This would not have been possible without your support and dedication! To learn everything about the changes, read on! What's new? TL;DR Key features: Reimplemented container engines support from scratch; A Kubernetes operator is taking shape; Falco's config_files configuration gained support to specify the merge strategy; Modern eBPF driver is now capable of trying to load multiple programs for each event; consequently, sendmmsg and recvmmsg will now make use of bpf_loop eBPF helper where available, boosting their performances; New proc.aargs field available, ie: a lookup for an ancestor args field; proc.args gained support for indexed access, to only check a certain argument; json_include_output_fields configuration key for Falco to control whether output fields are included in the JSON message; Ongoing work to improve libs code modularity; Key fixes: Avoid kmod crashing when a CPU gets enabled at runtime; Fixed Falco Prometheus metrics with multiple event sources enabled; Fixed RPM packages evaluation of RPM scripts; -o options do now correctly override included config_files; This release also comes with breaking changes that you should be aware of before upgrading. Major features and improvements The 0.41.0 release contains a number of features and UX improvements. Here is a list of some of the key new capabilities. Reimplemented container engines support In the Falco 0.41.0 release, the Falco team has completely revised its support for container engines. Key improvements include: Container support is now a plugin; The plugin will attach a listener to the eng ## Keycloak 26.2.4 released DevFeed: [Keycloak 26.2.4 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-05-08T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [OpenID connect (OIDC)](), [podman](), [istio]() Tags: [bugs](), [changes](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [openid-connect](), [release](), [saml](), [sso]() ### AI overview Keycloak 26.2.4 was released on May 8, 2025. The release includes an enhancement to the Podman documentation and resolves bugs involving login, IPv6 broker tests, offline-session token expiration values, UI performance, Infinispan, and the operator discovery service. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #39418 Clarify when to use podman docs Bugs #35278 Double click on social provider link causes page has expired error login/ui #38918 IPv6 support: Broker tests failing with proxy configuration ci #39021 After migrating to newer Keycloak, token refreshes using inherited offline sessions return access tokens with invalid exp value oidc #39023 Keycloak 26.2.0 UI Performance Degradation admin/ui #39173 duplicate key value violates unique constraint "constraint_offl_cl_ses_pk3" infinispan #39454 JGroups errors when running a containerized Keycloak in Strict FIPS mode and with Istio infinispan #39500 Update Job Pod is listed in the keycloak discovery service operator ## Keycloak 26.2.2 released DevFeed: [Keycloak 26.2.2 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-04-30T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authentication](), [ci](), [migration]() Tags: [bugs](), [changes](), [ci](), [cve](), [fips](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [migration](), [openid-connect](), [release](), [saml](), [sso](), [tests](), [timeout](), [verification]() ### AI overview Keycloak 26.2.2 was released on April 30, 2025. The release includes a configurable distribution startup timeout, CI FIPS crypto tests, and fixes for a two-factor authentication bypass and hostname verification issues. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #39142 Make distribution startup timeout configurable testsuite Bugs #39125 [Keycloak CI] - FIPS UT - Run crypto tests ci #39349 CVE-2025-3910 Two factor authentication bypass #39350 CVE-2025-3501 Keycloak hostname verification ## Keycloak Client Libraries 26.0.5 released DevFeed: [Keycloak Client Libraries 26.0.5 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-04-15T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [releases](), [client](), [Java]() Tags: [bugs](), [changes](), [idm](), [java](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [new-features](), [openid-connect](), [release](), [release-notes](), [saml](), [sso](), [testing](), [update]() ### AI overview Keycloak Client Libraries 26.0.5 was released on April 15, 2025. The release notes list new features, enhancements, testing updates, synchronization with Keycloak server 26.2, and a bug involving invalid SCM URLs in the POM. ### Source excerpt Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues New features #120 Add release notes so they can be pulled into the website client Enhancements #111 Close session when client is closed client #135 Testing and document keycloak-client with Java 11 client #147 Update PR-CHECKLIST client #158 Sync with Keycloak server after Keycloak 26.2 release client Bugs #150 POM contains invalid SCM URLs client [Next page]()