These working groups were recently created. Check them out!
No real update, still work in progress.
In the past month, the WG - Offering Metadata and Tooling Integration has made significant progress by closing several important issues. Notably, the group successfully implemented offering-based filtering, enhanced the ability to add filters using OR logic, and introduced a wildcard filter to display all extensions associated with a specific tag key, such as redhat-support. No new issues were opened during this period, indicating a focus on consolidating efforts and refining existing features.
(This status update was automatically generated using AI.)
In the last month, the WG - Observability.Next focused on improving the observability stack within the Quarkus framework. The group successfully closed several issues, addressing duplicated OpenTelemetry metrics messages and resolving test failures related to constructor injection in @GrpcService-annotated classes. Additionally, they worked on enhancing documentation regarding the differences in semantic conventions between Micrometer and OpenTelemetry. Notably, a new documentation issue was opened to further refine the precision of this section, reflecting ongoing efforts to clarify and improve resources for users.
(This status update was automatically generated using AI.)
We identified several improvements we want to make for Quarkus 4, typically related to Vert.x 5/ Netty 4.2 (to support HTTP/3, gRPC transcoding, etc.).
In the past month, the WG - Gizmo 2 made notable progress by successfully closing several issues related to various technical enhancements and optimizations. Key improvements included fixing reversed body handling in switch
, addressing caching for SAM locations, and reducing itable stub hits. The team also introduced new methods to streamline the handling of generic types and made efficiency improvements in ExecutableCreatorImpl
. However, all the closed issues have also been reopened, indicating ongoing work and potential refinement needed for these tasks.
(This status update was automatically generated using AI.)
Working group started.
In the past month, the WG - Chappie made strides in enhancing AI features within Quarkus Dev Mode by closing two key issues. The group addressed a problem where refreshing the workspace was not loading the assistant and successfully implemented a use case for computing HQL/SQL from English queries. No new issues were opened during this period, suggesting a concentrated effort on refining and solidifying the current functionalities.
(This status update was automatically generated using AI.)
In the last month, the WG - Test classloading achieved important milestones by successfully closing two issues related to test execution. They resolved problems with continuous testing failing in multi-module projects and addressed failures of QuarkusTests with nested classes in the IDEA IDE. However, a new issue was opened regarding the QuarkusTestProfileAwareClassOrderer, which no longer adheres to its expected contract, indicating ongoing challenges in refining the test classloading process.
(This status update was automatically generated using AI.)
In the past month, the WG - Dev Services Lifecycle made significant progress by closing essential issues related to the new dev services model. The team successfully transitioned AWS Lambda to the updated model, initiated services after augmentation, and added a runtime module for quarkus-devservices. However, a new issue was opened concerning the unintended startup of Keycloak dev services during the augmentation phase, along with another issue related to the QuarkusTestProfileAwareClassOrderer, indicating continued work needed to enhance the developer experience.
(This status update was automatically generated using AI.)
In the last month, the WG - OIDC improvements made notable progress by successfully closing an issue related to flow-specific OIDC request/response filter support, enhancing the overall functionality of quarkus-oidc. No new issues were opened during this period, indicating a focused effort on refining existing features and implementing critical security enhancements. The group continues to prioritize its objectives to further improve OIDC request interception and support for JWT bearer client authentication in the authorization code flow.
(This status update was automatically generated using AI.)
LRA dev service almost done!
On track, @FroMage is still working on Panache 2.
switch
MethodTypeDesc
switch
String
 as map keys instead of ClassDesc
 for generic types and boxing computationsArrayDeque
 trivially when possibleswitch
MethodTypeDesc
switch
String
 as map keys instead of ClassDesc
 for generic types and boxing computationsArrayDeque
 trivially when possible