# deprecated Published articles for deprecated. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Android A2UI (AI to UI) Made Simple DevFeed: [Android A2UI (AI to UI) Made Simple]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-09T07:23:57Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Artificial Intelligence](), [Android](), [Jetpack Compose](), [Mobile](), [Protocol (disambiguation)](), [Google]() Tags: [a2ui](), [ai](), [android](), [android-app-development](), [api](), [artificial-intelligence](), [deprecated](), [google](), [jetpack-compose](), [mobile-app-development](), [software-development](), [user-interfaces]() ### AI overview This tutorial introduces A2UI, a protocol for rendering AI responses as user interfaces, and discusses trying it on Android with Jetpack Compose. It notes that an older Jetpack A2UI library is deprecated and that newer development is ongoing. ### Source excerpt Converting AI Prompt Output Into User Interface in Jetpack Compose Continue reading on Mobile App Development Publication " ## Amazon EKS is replacing the deprecated aws-auth ConfigMap for IAM-to-cluster permission mapping DevFeed: [Amazon EKS is replacing the deprecated aws-auth ConfigMap for IAM-to-cluster permission mapping]() Original publisher: [Read original article]() Author: Yannick Struyf Published: 2026-08-19T18:59:54Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Amazon EKS](), [Kubernetes](), [AWS IAM](), [Access Control](), [Amazon Web Services](), [Cloud](), [migration]() Tags: [access-control](), [amazon-eks](), [aws](), [cloud](), [cloud-native](), [deprecated](), [iam](), [kubernetes](), [migration](), [nutanix](), [platform-engineering](), [post](), [report](), [security](), [sponsor-nutanix](), [sponsored](), [sponsored-post]() ### AI overview The article examines security challenges in Kubernetes and cloud-native infrastructure, focusing on Amazon EKS's replacement of the deprecated aws-auth ConfigMap with an API-driven method for mapping IAM identities to cluster permissions. It also explains how Kubernetes security spans code, containers, clusters, and cloud infrastructure. ### Source excerpt The migration to Kubernetes and cloud native infrastructure has been one of the defining IT trends of the past decade. The post AWS deprecated this EKS auth method. 81% of clusters still run it. appeared first on The New Stack. ## Announcement: Xcode16 Deprecation in Semaphore DevFeed: [Announcement: Xcode16 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-08-04T13:47:48Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [macOS](), [ci]() Tags: [announcement](), [ci](), [deprecated](), [end-of-life](), [lifecycle](), [macos](), [operating-systems](), [product-news](), [yaml]() ### AI overview Semaphore is deprecating and retiring its macOS Xcode16 build environments. Brownout periods will run from September 7 through October 4, 2026, before the environments are removed on October 5, 2026. Users are instructed to migrate pipelines to macos-xcode26 and validate them. ### Source excerpt MacOS Xcode16 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode16 build environments. Semaphore users should switch to Xcode26. Why We're Deprecating Xcode16 As operating systems age, they cease to receive timely security [...] The post Announcement: Xcode16 Deprecation in Semaphore appeared first on Semaphore. ## Introducing Graph API v26.0 and Marketing API v26.0 DevFeed: [Introducing Graph API v26.0 and Marketing API v26.0]() Original publisher: [Read original article]() Published: 2026-07-29T17:00:36Z Content type: release Language: en Sources: [Facebook Developers]() Topics: [API](), [changelog]() Tags: [ads](), [api](), [changelog](), [checkout](), [deprecated](), [errors](), [facebook](), [instagram](), [whatsapp]() ### AI overview Graph API v26.0 and Marketing API v26.0 introduce new capabilities, deprecations, and breaking changes. The article highlights WhatsApp Status ad capabilities, removal of deprecated delivery estimate fields, and deprecation of Commerce Order Management API endpoints for the sunset Facebook and Instagram Shops checkout experience. ### Source excerpt Graph API v26.0 and Marketing API v26.0 include new capabilities, deprecations, and breaking changes. Review the highlights below and visit the V26.0 changelog for the complete list of changes and details. ## Migrating from Apollo Tooling to GraphQL Codegen at Yelp DevFeed: [Migrating from Apollo Tooling to GraphQL Codegen at Yelp]() Original publisher: [Read original article]() Author: Igor Kusakov, Software Engineer Published: 2026-07-16T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [GraphQL](), [Code generation](), [migration](), [Tooling](), [React](), [TypeScript](), [monorepo]() Tags: [code-generation](), [deprecated](), [graphql](), [migrate](), [monorepo](), [react](), [tooling](), [typescript]() ### AI overview Yelp describes migrating its frontend React monorepo from deprecated Apollo Tooling to GraphQL Codegen for generating TypeScript definitions from GraphQL queries and the server schema. ### Source excerpt Introduction At Yelp, we rely heavily on GraphQL and Apollo for data loading in our frontend React monorepo. When a developer writes a GraphQL query or mutation inside a React component, the shape of the response is defined by the query itself -- but TypeScript has no way to know what that shape looks like at compile time. That's where code generation (codegen) comes in. We rely on codegen to read our queries and server schema, then produce TypeScript type definitions for every operation's input variables and output data. In our codebase, this looks like: src/components/UserProfile/ ├── UserProfile.tsx <- contains... ## Keycloak 26.7.0 released DevFeed: [Keycloak 26.7.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-07-09T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [API](), [Authentication](), [Authorization](), [Security](), [OAuth 2.0](), [saml]() Tags: [api](), [authentication](), [authorization](), [deprecated](), [haproxy](), [high-availability](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [oauth](), [oauth-2-0](), [openid-connect](), [persistence](), [provisioning](), [release](), [saml](), [security](), [sso](), [traefik]() ### AI overview Keycloak 26.7.0 introduces preview support for SCIM-based user provisioning and simplified multi-cluster high availability, along with enhanced HAProxy and Traefik reverse-proxy guidance and step-up authentication for SAML clients. The release also adds a more secure, OAuth 2.0-compliant Identity Brokering API v2, while V1 remains enabled by default but is deprecated. OID4VCI improvements remain experimental. ### Source excerpt To download the release go to Keycloak downloads. Highlights This release features new capabilities for users and administrators of Keycloak. The highlights of this release are: Automate user provisioning with the SCIM API (preview) Simplified multi-cluster high availability without external caches (preview) Enhanced reverse proxy guides with blueprints for HAProxy and Traefik Step-up authentication for SAML clients Read on to learn more about each new feature. If you are upgrading from a previous release, also review the changes listed in the upgrading guide. Security and Standards Stronger security for the Identity Brokering API The Identity Brokering API allows applications to retrieve tokens obtained from external identity providers during federated login. Version 2 of this API replaces the legacy V1 with a more secure and standards-compliant design: Client-level authorization -- access to external tokens is controlled per client using dedicated settings (Allow retrieve external tokens and an identity provider allow list) instead of assigning broker roles to individual users. Confidential clients only -- public clients are rejected, ensuring that only authenticated clients can retrieve external tokens. OAuth 2.0 compliant -- the endpoint uses POST and returns standard JSON responses with access_token, error, and error_description fields. Session-based token storage -- a new Store token in session option keeps tokens in the user session for faster access, with automatic cleanup on session expiry. Database storage remains available for persistence across sessions. V2 is now supported but disabled by default. V1 is deprecated but still enabled by default for backward compatibility. In a future release, V1 will be removed and V2 will become the default. For more information, see the Identity Brokering APIs chapter in the Server Developer Guide. Progress on Verifiable Credentials (OID4VCI) (experimental) Verifiable Credentials (OID4VCI) allow organizations to issue tampe ## Vulkan Ray Tracing: Deprecating Host-Side Acceleration Structure Builds DevFeed: [Vulkan Ray Tracing: Deprecating Host-Side Acceleration Structure Builds]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-07-08T13:00:00Z Content type: article Language: en Sources: [Blogs Khronos Blog]() Topics: [Ray Tracing](), [GPU](), [Hardware]() Tags: [api](), [architecture](), [blog](), [complexity](), [deprecated](), [gpu](), [hardware](), [migration](), [ray-tracing](), [vulkan]() ### AI overview Vulkan is deprecating host-side ray tracing acceleration structure build commands in favor of a device-address-based path. Existing applications remain functional, while developers using host-side commands should plan migration to device-side equivalents. ### Source excerpt Vulkan is deprecating host-side ray tracing acceleration structure build commands in favor of a single, device-address-based path. This aligns Vulkan Ray Tracing with the direction of DirectX Raytracing, modern engine architecture, and hardware trends. In the six years since Vulkan Ray Tracing launched, the host-side path has seen limited adoption. Developers generally found it more cumbersome than helpful, while implementers had to maintain parallel host/GPU command models that increased complexity and created friction for future ray tracing API evolution. ## Deprecating OpenCensus compatibility requirements DevFeed: [Deprecating OpenCensus compatibility requirements]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-06-19T22:53:47Z Content type: news Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [deprecated](), [migration](), [SDKs]() Tags: [deprecated](), [java](), [javascript](), [migrate](), [migration](), [opentelemetry](), [python](), [sdks]() ### AI overview The OpenTelemetry Specification project deprecated OpenCensus compatibility requirements on June 12, 2026. New SDKs and implementations no longer need to add OpenCensus compatibility, while existing shims may continue receiving maintenance during the deprecation period. New work should use native OpenTelemetry APIs, SDKs, and OTLP-based workflows. ### Source excerpt On June 12, 2026, the OpenTelemetry Specification project merged PR #5138, deprecating OpenCensus compatibility requirements in the specification. This change updates the specification to match where the ecosystem already is: OpenCensus has been archived since July 31, 2023, and the OpenTelemetry shims for OpenCensus have provided a stable migration bridge for more than three years. This is a deprecation of specification requirements, not an immediate removal of compatibility material and not a requirement to remove existing shim artifacts right away. ## NixOS 26.05 released DevFeed: [NixOS 26.05 released]() Original publisher: [Read original article]() Author: NixOS Published: 2026-05-30T07:00:00Z Content type: release Language: en Sources: [NixOS Announcements]() Topics: [Nix](), [Linux](), [releases](), [Release notes](), [systemd](), [configuration](), [modules](), [deprecated](), [Package manager]() Tags: [2026](), [accessibility](), [configuration](), [deprecated](), [end-of-life](), [gcc](), [linux](), [llvm](), [macos](), [modules](), [nix](), [nixos](), [release](), [release-notes](), [systemd](), [x86-64]() ### AI overview NixOS 26.05, named "Yarara," is publicly available as a new Linux distribution release. The announcement covers package, module, configuration, systemd initrd, platform-support, GNOME, and compiler changes, along with support timelines for NixOS 26.05 and the previous 25.11 release. ### Source excerpt Hey everyone, we are yayayayaka and jopejoe1, the release managers of the newest release of NixOS. We are very proud to announce the public availability of NixOS 26.05 "Yarara". NixOS is a Linux distribution. Its underlying package repository Nixpkgs can also be used on other Linux systems and macOS with the Nix package manager. This release will receive bugfixes and security updates for seven months (up until 2026-12-31). The old release 25.11 "Xantusia" is now officially deprecated and will reach its end-of-life and stop receiving security updates after 2026-06-30. NixOS Release Notes Highlights New Modules Backward Incompatibilities Other Notable Changes Nixpkgs Release Notes Highlights Backward Incompatibilities Other Notable Changes Nixpkgs Library Upgrade Instructions ISO Image Downloads The 26.05 release was made possible due to the efforts of 2842 contributors, who authored 59703 commits since the previous release. Highlights Our vast and routinely maintained set of packages has also been updated. This release of Nixpkgs Added 20442 new packages Updated 20641 existing packages Removed 17532 outdated packages, in an effort to keep the package set maintainable and secure. In addition to packages from Nixpkgs, the NixOS Linux distribution also features composable configuration modules and integration tests for distributed systems. This release of NixOS Added 85 new modules and 1547 configuration options Removed 25 outdated modules and 355 configuration options. systemd stage 1 Stage 1 (a.k.a. initrd) is now based on systemd by default, and the old scripted implementation is deprecated and scheduled for removal in 26.11. Deprecation of x86_64-darwin This will be the last release of Nixpkgs to support x86_64-darwin. Platform support will be maintained and binaries built until Nixpkgs 26.05 goes out of support at the end of 2026. For 26.11, due to Apple's deprecation of the platform and limited build infrastructure and developer time, we will no longer build packa ## Autofilling in the Blanks DevFeed: [Autofilling in the Blanks]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-05-29T09:05:36.887000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Compose](), [Android](), [Accessibility](), [Usability](), [Forms](), [API]() Tags: [accessibility](), [android](), [api](), [compose](), [deprecated](), [forms](), [usability]() ### AI overview This tutorial explains how autofill can improve accessibility and usability in Android forms. It describes autofill services and settings, then shows how Jetpack Compose uses the semantics-based autofill API after the previous Autofill API was deprecated with Compose 1.8.0. ### Source excerpt If you have forms in your app that collect user information, autofill is one of the easiest accessibility wins you can add. Autofill is both an accessibility and a usability feature. And you can support it with just a few lines of code. What is Autofill? So, what is autofill, anyway? It's a technique that uses previously saved data to fill in text fields without having to type the full text. Typically, the data types are related to the user's name, address, email, or password, to mention a couple of examples. There are different autofill services for Android; some provide more data than others. Most of them are various password managers, but Google's service, for instance, also provides account-related data. You can find the autofill settings in your phone's settings. On Pixel, the setting group is called "Passwords, passkeys and accounts". You'll need to set a service as the preferred one to make autofill work properly. Autofill is also an accessibility feature. Let's look into that next. Autofill is an Accessibility Feature Supporting autofill for form fields helps people of all kinds. For example, if typing is difficult for you for any reason, like limited mobility, trembling hands, or fingers freezing outside, being able to use autofill services makes your life so much easier. Autofill also helps with avoiding spelling mistakes - when the data is already available and can be just filled out, you don't need to stress about making mistakes when writing your address, for example. And autofill makes it faster if you're in a hurry and need to buy a ticket somewhere. So, autofill has many great use cases. But how do you support it? Let's look at the details. Autofill and Compose Compose used to have an Autofill API for requesting autofill, but it was deprecated with Compose 1.8.0. Autofill is now requested with the new semantics-based autofill API. Supported Types As mentioned before, autofill supports different kinds of data. I'll list some of the types: Address-rela ## Blog: Introducing Falco 0.44.0 DevFeed: [Blog: Introducing Falco 0.44.0]() Original publisher: [Read original article]() Published: 2026-05-26T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [eBPF](), [Kernel](), [Command-line interface](), [Kubernetes]() Tags: [cli](), [deprecated](), [ebpf](), [falco](), [kernel](), [kubernetes](), [release](), [version]() ### AI overview Falco 0.44.0 removes the legacy eBPF probe, gVisor engine, and gRPC output and server. The release adds rule-language list modifiers, a hard capture-file size limit, stricter schema validation, JSON output for listing commands, faster process-tree lookups, and multi-thread safety fixes. It also includes updated libraries, drivers, plugins, and rules. ### Source excerpt Dear Falco Community, we are happy to announce the release of Falco 0.44.0 today! This release completes the deprecation cycle started in 0.42.0 and 0.43.0: the legacy eBPF probe, the gVisor engine, and the gRPC output (along with the gRPC server) are now fully removed from the entire stack. On top of that, 0.44.0 brings new rule-language capabilities, a long-requested safety knob for the capture feature, JSON output for the --list family of commands, a substantial round of performance work on process tree lookups, and a wave of multi-thread safety fixes that lay the groundwork for the upcoming multi-threaded Falco architecture. During this release cycle, we merged: 60 PRs on Falco, including 14 release note-worthy changes 160 PRs on Falco libs, including 54 release note-worthy changes 16 PRs on Falco drivers, including 3 release note-worthy changes We upgraded libs to version 0.25.2 and drivers to 10.2.0+driver. We also ship falcoctl 0.13.0, the container plugin 0.7.1, and the falco-rules ruleset 5.1.0. 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 Major features and improvements: Comparison operator list modifiers (oneof/anyof/allof) Hard limit on capture file size Stricter rule schema validation Backslash escaping in -o dotted key paths JSON output for the listing CLI commands Faster process tree lookups Multi-thread safety hardening Drivers: The kernel module pre-builds for this release are still being produced and will be available within a couple of days from the release. In the meantime, falcoctl can build the kernel module locally on the host. Drivers: new syscall, kernel 7.0, and BPF iterators Plugins: Container plugin fix for containerd v2.3.0 Plugin library path traversal hardening Event generator: Event generator: HTTP output and new suite namespace Rules: Updated ruleset (falco-rules 5.1.0) Kubernetes: Kubernetes Oper ## Announcement: Xcode15 Deprecation in Semaphore DevFeed: [Announcement: Xcode15 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-05-12T10:56:42Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [ci](), [macOS]() Tags: [announcement](), [ci](), [deprecated](), [lifecycle](), [product-news](), [scheduled](), [september-2026](), [switching](), [xcode]() ### AI overview Semaphore announces the deprecation and end of life of its macOS Xcode15 build environments. Brownout periods will precede removal on July 6, 2026, and users are advised to migrate their pipelines to a supported Xcode version, preferably Xcode26. ### Source excerpt MacOS Xcode15 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode15 build environments. Semaphore users should consider switching to Xcode26 as Xcode16 is scheduled for deprecation in September 2026. Why We're Deprecating Xcode15 [...] The post Announcement: Xcode15 Deprecation in Semaphore appeared first on Semaphore. ## SecDB is the past, OSV is the future DevFeed: [SecDB is the past, OSV is the future]() Original publisher: [Read original article]() Published: 2026-04-09T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard containers](), [vulnerability](), [Vulnerabilities](), [chainguard packages](), [Security]() Tags: [chainguard](), [chainguard-containers](), [chainguard-scanners](), [cves](), [deprecated](), [open-source-vulnerabilities](), [osv](), [secdb](), [security](), [vulnerability](), [vulnerability-data](), [vulnerability-scanning]() ### AI overview Chainguard is deprecating its SecDB vulnerability feed and plans to sunset it at the end of 2026. The company is moving toward the OSV schema because it supports more precise vulnerability data, including unfixed vulnerabilities and component-level advisory details. ### Source excerpt Chainguard is deprecating SecDB in favor of OSV, delivering more accurate, granular vulnerability data and better visibility for modern software supply chains. ## Docs on autopilot: From zero to self-maintaining with Mintlify DevFeed: [Docs on autopilot: From zero to self-maintaining with Mintlify]() Original publisher: [Read original article]() Author: Peri Langlois Published: 2026-04-03T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [GitHub](), [API]() Tags: [audits](), [best-practices](), [broken-links](), [changelog](), [deprecated](), [docs](), [documentation](), [feature](), [features](), [generate](), [github](), [pull-request]() ### AI overview Mintlify presents auto-generated documentation and Automations that can create a docs site from a GitHub repository and keep documentation updated as code changes. Automations can sync docs after pushes, generate changelogs, audit documentation, and draft pages for new features. ### Source excerpt How Mintlify's auto-generated docs and automations combine to take documentation from nonexistent to self-maintaining. ## Jetpack's evolution, ecosystem complexity, and a curated Android development stack DevFeed: [Jetpack's evolution, ecosystem complexity, and a curated Android development stack]() Original publisher: [Read original article]() Author: Thomas Künneth Published: 2026-03-08T11:36:03Z Content type: tutorial Language: en Sources: [Thomas Künneth]() Topics: [Jetpack](), [Android](), [android-development](), [Library](), [Architecture & Design](), [migration]() Tags: [android](), [android-architecture](), [android-development](), [architecture-components](), [coding](), [community](), [compatibility](), [dependency](), [deprecated](), [development](), [ecosystem](), [engineering](), [inclusive](), [jetpack](), [jetpackcompose](), [kmp](), [kotlin](), [library](), [migration](), [software]() ### AI overview This article traces Jetpack's evolution from Android Architecture Components and the Support Library to Jetpack and the androidx namespace. It argues that Jetpack's growth to more than 130 artifacts, along with deprecated libraries and multiple solutions for common tasks, has created an ecosystem that developers need to navigate using a curated recommended stack. ### Source excerpt If you are an Android developer, you know Jetpack. It changed how we build Android apps. But that was long ago. Today, the ecosystem is shifting again. We aren't just building for one platform anymore. We are building for the world. Let me show you how to take the Jetpack libraries you know and use them to fuel a new generation of applications that run everywhere. From Jetpack to a unified architecture First, let's ground ourselves. What exactly is Jetpack? It's more than just a bag of libraries. It is Google's opinionated answer to Android development. It unbundled features from the OS, so we could update our apps without waiting for Android system updates. It gave us backward compatibility. Most importantly, it gave us guidance. It stopped the wild west of Android development and brought us a standard way to build. Before Jetpack, we lived in an era of fragmentation. New features were tied to the OS. If you wanted the latest UI on an older phone, you were out of luck. Eventually, Google introduced the Support Library to fix this. It sort of worked, but it was a mess. We had v4 support, v7 appcompat, v13... it was dependency hell. We needed a reboot. That reboot came in two steps. In 2017, Google announced Android Architecture Components at I/O--ViewModel, Room, Lifecycle, LiveData--and they went 1.0 stable that November. That was the how to architect piece. Then, at I/O 2018, came Jetpack: the umbrella name and the migration to androidx.*. Eventually, everything moved to the new namespace. Libraries were strictly unbundled--own versions, own cycles, semantic versioning so we could reason about compatibility. So: Architecture Components in 2017, Jetpack and androidx in 2018. Today, we have solved one problem but created another: The Jetpack Jungle. There are now over 130 artifacts in the suite. We have historical baggage. Deprecated libraries still sit next to modern ones--for example lifecycle-extensions, which Google deprecated and replaced with separate lifecycle-ru ## Deprecating Arquillian Testsuite, Keycloak Test Framework Full Support DevFeed: [Deprecating Arquillian Testsuite, Keycloak Test Framework Full Support]() Original publisher: [Read original article]() Author: Lukas Hanusovsky Published: 2026-02-25T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [test]() Tags: [announcement](), [deprecated](), [features](), [idm](), [kerberos](), [keycloak](), [ldap](), [new-features](), [openid-connect](), [release](), [saml](), [sso](), [test]() ### AI overview Keycloak is deprecating the testsuite module and related Arquillian testsuite dependents, while beginning full support for the JUnit 6-based Keycloak Test Framework in the upcoming Keycloak 26.6.0 release. Contributors are encouraged to migrate tests to the new tests module, which provides lifecycle management and features for testing Keycloak and extensions. ### Source excerpt What's changing? The testsuite module, with all related dependents, like Arquillian testsuite, is now officially deprecated. At the same time Test Framework full support is starting from the upcoming Keycloak 26.6.0 release. The New Test Framework Based on JUnit 6, the Keycloak Test Framework makes it easy to write tests for Keycloak and extensions. Behind the scenes the framework handles the lifecycle of Keycloak, the database, and any injected resources such as realms and clients. Tests simply declare what they want, including specific configuration, and the framework takes care of the rest. Contributors are asked to start using new Test Framework and write tests within the new tests module. What's new? Since the initial announcement these new features have been added: Improved documentation Improved registry with dependency graph Hot deploy with external providers Re-use support for distribution server, for faster execution times Re-use support for H2 database, for faster execution times Managed OAuth client Managed Admin client factory Support for conditional execution (e.g.disable tests for certain databases) @TestSetup and @TestCleanup method annotation to configure a specific test class TimeOffset support Test framework unit and integration tests Test framework injection validation Run on Server functionality TLS and mTLS with managed certificates FIPS with managed crypto keys Managed Infinispan server Managed Email server Managed HTTP client and HTTP server Events and Admin Events assertions Custom providers support GitHub Actions summary report Test suites support Clustering support WebAuthn support Migration util On top of that, the whole admin tests package has been migrated. My first test The following shows a very simply test that deploys a realm to Keycloak and creates a user within the realm. @KeycloakIntegrationTest public class MyInitialTest { @InjectRealm ManagedRealm realm; @InjectUser ManagedUser user; @Test public void myFirstTest() { Assertions ## JWT Authorization Grant and Identity Chaining in Keycloak 26.5 DevFeed: [JWT Authorization Grant and Identity Chaining in Keycloak 26.5]() Original publisher: [Read original article]() Author: Giuseppe Graziano Published: 2026-01-23T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [JSON Web Tokens](), [Keycloak](), [OAuth 2.0](), [OAuth](), [Authorization](), [Internet Engineering Task Force (IETF)]() Tags: [authorization](), [deprecated](), [external](), [identity](), [idm](), [jwt](), [kerberos](), [keycloak](), [ldap](), [oauth](), [oauth-2-0](), [openid-connect](), [preview](), [saml](), [sso](), [standard](), [trust]() ### AI overview Keycloak 26.5 introduces preview support for JWT Authorization Grant under RFC 7523. The feature lets clients exchange a signed JWT from an external issuer for a Keycloak access token. The article also explains how combining this grant with OAuth 2.0 Token Exchange can preserve identity and authorization context across multiple trust domains. ### Source excerpt Modern applications and AI agents increasingly operate across distributed trust domains, where each domain is protected by its own OAuth 2.0 Authorization Server. A single request may also traverse multiple resource servers to complete a task. This raises an important challenge: every protected resource must understand who initiated the request, which authorization was granted, and optionally which other resources were accessed before making an authorization decision. Preserving this information across domains is critical. Keycloak 26.5 introduces preview support for the new feature JWT Authorization Grant, implementing RFC 7523. This feature allows a client to present a signed JWT from an external issuer and obtain a Keycloak access token, providing a standard and secure way to authorize requests based on external assertions. However, exchanging a token alone does not fully solve the problem of propagating identity and authorization context across multiple trust domains. The IETF draft OAuth Identity and Authorization Chaining Across Domains defines a standardized flow that combines JWT Authorization Grant (RFC 7523) with OAuth 2.0 Token Exchange (RFC 8693), which Keycloak already supports, to preserve the original user's identity, claims, and authorization throughout the chain. JWT Authorization Grant The JWT Authorization Grant feature allows a client to present a signed JWT assertion to the token endpoint and obtain an access token without an interactive authorization step. To initiate this flow, the client sends a request to the token endpoint with the grant_type set to urn:ietf:params:oauth:grant-type:jwt-bearer and the external token passed in the assertion parameter. It provides a standard and secure alternative to the preview feature External-to-Internal Token Exchange V1 which will be deprecated. Trust relationships in Keycloak are defined through Identity Providers. The JWT Authorization Grant can be enabled and configured in a dedicated section of the ex ## IPLD 2025 Review: From Monoliths to Modules DevFeed: [IPLD 2025 Review: From Monoliths to Modules]() Original publisher: [Read original article]() Author: Volker Mische Published: 2026-01-19T00:00:00Z Content type: article Language: en Sources: [IPFS]() Topics: [Rust](), [modules](), [migration](), [IPFS](), [AT Protocol](), [deprecated]() Tags: [deprecated](), [ipfs](), [migration](), [modules](), [object-object](), [protocol](), [rust]() ### AI overview The article reviews progress in the IPLD ecosystem during 2025 and previews work for 2026. It describes the Rust IPLD implementation's migration to separate crates, its deprecation, improved performance for Python DAG-CBOR and Bluesky custom feeds, and a migration path to Serde-based crates. ### Source excerpt The year that brought us modular Rust libraries, faster DAG-CBOR, stable multiformats, and a simpler on-ramp with DASL. ## install.md: A Standard for LLM-Executable Installation DevFeed: [install.md: A Standard for LLM-Executable Installation]() Original publisher: [Read original article]() Author: Michael Ryaboy Published: 2026-01-15T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Agent Skills](), [Documentation](), [Large Language Model](), [Artificial Intelligence](), [Claude]() Tags: [agent-skills](), [announcement](), [announcements](), [deprecated](), [documentation](), [llm]() ### AI overview The article proposes install.md as a standard, human-readable file for LLM-executable software installation instructions. It explains that agents can read the file, detect the environment, adapt setup steps, and optionally request approval. The article also states that install.md was deprecated on January 21, 2026, in favor of skill.md, an open standard for agent skills covering installation and usage knowledge. ### Source excerpt A proposal for a standard /install.md file that provides LLM-executable installation instructions. ## The best way to replace the deprecated GenericGenerator DevFeed: [The best way to replace the deprecated GenericGenerator]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-12-02T08:23:12Z Content type: tutorial Language: en Sources: [Vlad Mihalcea]() Topics: [Java](), [Development](), [Spring Boot](), [Code](), [Jakarta EE]() Tags: [article](), [database-identifier](), [deprecated](), [genericgenerator](), [hibernate](), [how-to](), [identifier](), [java](), [jpa](), [tsid]() ### AI overview This tutorial explains how to replace the deprecated Hibernate @GenericGenerator annotation when upgrading an application to Hibernate 7. It covers custom entity identifier generators and sequence optimizers using the @IdGeneratorType meta-annotation. ### Source excerpt Introduction In this article, I'm going to show you the best way to replace the deprecated @GenericGenerator when upgrading your application to Hibernate 7. Hibernate @GenericGenerator annotation The @GenericGenerator annotation has been available since Hibernate 3.5, as an alternative to the XML element from HBM mappings. As illustrated by the Hibernate 6.5 @GenericGenerator Javadoc, this annotation was deprecated in favor of the @IdGeneratorType meta-annotation, which we've been using before for the TSID identifier. Traditionally, there were two main use cases where you'd use the @GenericGenerator annotation: to provide a custom identifier... Read More The post The best way to replace the deprecated GenericGenerator appeared first on Vlad Mihalcea. ## NixOS 25.11 released DevFeed: [NixOS 25.11 released]() Original publisher: [Read original article]() Author: NixOS Published: 2025-11-30T16:00:00Z Content type: release Language: en Sources: [NixOS Announcements]() Topics: [Nix](), [Linux](), [Release notes](), [version](), [configuration](), [modules](), [CMake](), [gcc](), [LLVM]() Tags: [2026](), [bugfixes](), [cmake](), [compilers](), [deprecated](), [end-of-life](), [gcc](), [linux](), [llvm](), [nix](), [nixos](), [nixpkgs](), [release](), [release-notes](), [version]() ### AI overview NixOS 25.11 "Xantusia" is publicly available. The release updates Nixpkgs with new, updated, and removed packages; adds configuration modules and options; updates GNOME to version 49, LLVM to version 21, and CMake to version 4; and provides bugfix and security updates through June 30, 2026. ### Source excerpt Hey everyone, we are jopejoe1 and Leona Maroni, the release managers of the newest release of NixOS. We are very proud to announce the public availability of NixOS 25.11 "Xantusia". NixOS is a Linux distribution. Its underlying package repository Nixpkgs can also be used on other Linux systems and macOS with the Nix package manager. This release will receive bugfixes and security updates for seven months (up until 2026-06-30). The old release 25.05 "Warbler" is now officially deprecated and will reach its end-of-life and stop receiving security updates after 2025-12-31. NixOS Release Notes Highlights New Modules Backward Incompatibilities Other Notable Changes Nixpkgs Release Notes Highlights Backward Incompatibilities Other Notable Changes Nixpkgs Library Upgrade Instructions ISO Image Downloads The 25.11 release was made possible due to the efforts of 2742 contributors, who authored 59430 commits since the previous release. Highlights Our vast and routinely maintained set of packages has also been updated. This release of Nixpkgs Added 7002 new packages Updated 25252 existing packages Removed 6338 outdated packages, in an effort to keep the package set maintainable and secure. In addition to packages from Nixpkgs, the NixOS Linux distribution also features composable configuration modules and integration tests for distributed systems. This release of NixOS Added 107 new modules and 1778 configuration options Removed 41 outdated modules and 807 configuration options. GNOME 49 GNOME has been updated to version 49 "Brescia", which removes X11 session support, introduces a new video player, a new document viewer, a redesigned calendar and more changes. Refer to the release notes for more details. C compilers LLVM has been updated to version 21. GCC remains at version 14. CMake was updated to version 4. Special Thanks We want to personally thank Seth and dish for editorializing the release notes Yohann Boniface for the release logo The NixOS infrastructure team for the ## Impact of SHA1-Hulud: The Second Coming on the Mintlify CLI DevFeed: [Impact of SHA1-Hulud: The Second Coming on the Mintlify CLI]() Original publisher: [Read original article]() Author: Han Wang Published: 2025-11-25T00:00:00Z Content type: news Language: en Sources: [Mintlify Blog]() Topics: [Command-line interface](), [npm](), [malicious packages](), [Security](), [pnpm](), [GitHub](), [Cloud]() Tags: [announcements](), [deprecated](), [malicious-packages](), [npm](), [pnpm](), [resolved](), [security](), [sha1-hulud](), [supply-chain](), [upgrade]() ### AI overview Mintlify reports that its CLI was briefly exposed to the SHA1-Hulud supply chain attack through compromised npm dependencies on November 24, 2025. The company says it resolved the issue within six hours, released CLI version 4.2.210, deprecated potentially affected versions, and provided remediation steps for users who installed or updated during the vulnerable window. ### Source excerpt The Mintlify CLI was briefly exposed to a supply chain attack. Learn what happened, who was affected, and what actions to take. Resolved in 6 hours. ## Deprecations, Defaults, and Details: The Subtle Tweaks You Might Miss in OpenAPI 3.2 DevFeed: [Deprecations, Defaults, and Details: The Subtle Tweaks You Might Miss in OpenAPI 3.2]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-10-28T10:04:36Z Content type: article Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [deprecated](), [Documentation](), [Structured-data]() Tags: [deprecated](), [documentation](), [engineering](), [examples](), [features](), [openapi](), [schema](), [schemas]() ### AI overview This article explains less prominent refinements in OpenAPI 3.2, including broader deprecation support, clarified defaults, improved examples, and changes to schema references. These updates aim to make API specifications and generated documentation more consistent and predictable. ### Source excerpt OpenAPI 3.2 brings subtle refinements that make specs cleaner and more predictable, from improved deprecation handling to clarified defaults, schema rules, and examples. ## OpenAPI 3.2 adds OAuth device flow, structured tags, QUERY, streaming, and XML modeling DevFeed: [OpenAPI 3.2 adds OAuth device flow, structured tags, QUERY, streaming, and XML modeling]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-10-05T12:12:40Z Content type: article Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [OAuth](), [HTTP](), [Streaming](), [Tooling](), [XML]() Tags: [deprecated](), [engineering](), [event-streaming](), [extension](), [http](), [oauth](), [openapi](), [schema](), [streaming]() ### AI overview The article reviews proposed OpenAPI 3.2 changes, including OAuth device flow support, hierarchical tags, the QUERY method, clearer multipart definitions, streaming API support, and improved XML modeling. It describes the release as incremental and compatible with OpenAPI 3.1. ### Source excerpt See what's new in OpenAPI v3.2. Better structure, better auth support, better file and stream handling - no breaking changes. [Next page]()