Working Group Activities Report (April 26) #53830

cescoffier · 2026-04-27T15:21:56Z

cescoffier
Apr 27, 2026
Maintainer

New working groups

These working groups were recently created.
Check them out!

Completed working groups

These working groups are now completed.

Latest updates

🟢 WG - Java 25 support

We addressed the JIB issue regarding jvm-additional-arguments for AOT cache generation and updated the Deploy to Openshift guide for Java 25. Both are now back on the radar for further refinement. Also tracking a new Panache Next projection failure with Kotlin value classes.

(This status update was automatically generated using AI.)

🟢 WG - Quarkus 4

The team closed out significant work on the Vert.x 5 upgrade and migration of its core extension for Quarkus 4. New tasks include updating Vert.x configuration, reworking CI, and addressing Kafka Kerberos authentication in native mode. We're also defining OpenTelemetry trace sampling defaults and looking into extension modularity.

(This status update was automatically generated using AI.)

🟢 WG - Agentic Foundation and LangChain4j Next

Work continues defining the Agentic Foundation. Key focus areas remain MCP conformance tests, introducing Skills, and enabling CDI bean suppliers for @RegisterAiService. These items are seeing ongoing iteration and refinement.

(This status update was automatically generated using AI.)

🟢 WG - Unified Event Bus

The working group is now active.

🟢 WG - Modularity (JPMS) and JLink

Working Group Started

🟢 WG - Graceful Shutdown

Working Group started.

🟢 WG - Unified Saga implementation

We've enabled the Narayana JTA Recovery service by default. For Quarkus 3.27, the flaky LRA TCK tests were addressed, but they're still under active investigation.

(This status update was automatically generated using AI.)

🟢 WG - AOT Support

We've been deeply focused on AOT cache generation and container image builds. This includes addressing Jib's JVM argument handling, enhancing image configuration, and improving documentation for manual cache creation. Many of these areas remain active tasks as we also explore extension-based modularity for AOT.

(This status update was automatically generated using AI.)

🟢 WG - Observability.Next

For Observability.Next, the team is actively investigating a few key areas. We're looking into Micrometer Prometheus http_server_bytes_read registration issues with the management interface. We're also addressing correlated span problems in the Vert.x event bus and OpenTelemetry context loss for blocking @ConsumeEvent with fire-and-forget messages.

(This status update was automatically generated using AI.)

🟢 WG - Dev Star

Working Group Started.

🟢 WG - Quarkus Data

Much of our work on Panache Next, soon to be renamed Quarkus Data, involved resolving several operation overload issues and refining Hibernate Reactive type signatures. We also enabled StatelessSession injection. Now, the team is tackling transaction propagation with Vert.x Context, allowing mixed Session and StatelessSession, and fixing projection failures with Kotlin value classes.

(This status update was automatically generated using AI.)

🟢 WG - Dev Services Lifecycle

We've been focusing on improving Dev Services reliability. We fixed a dependency issue where quarkus-devservices-deployment wasn't correctly depending on quarkus-devservices. We also resolved an issue with Kafka Dev Service loading across different Docker networks.

(This status update was automatically generated using AI.)

🟢 WG - Spring-Style Testing

We've completed our initial exploration into the various testing approaches used by Spring developers. Currently, no new issues are open for the working group.

(This status update was automatically generated using AI.)