• Release Timeline: Quarkus 3.18.0 was released one month ago. Version 3.19.0 was released in February 2025 and is the last release before 3.20.0. 3.20.0 is feature complete and scheduled for March 26th.
• New Infrastructure: All core extensions use the new @ConfigMapping infrastructure except for some compatibility exceptions. It requires a public interface annotated with [@ConfigMapping](https://github.com/smallrye/smallrye-config/blob/main/implementation/src/main/java/io/smallrye/config/ConfigMapping.java).
• Configuration Example: An example of using @ConfigMapping is shown with an interface and setting values in an application.properties file. The interface can be injected into a CDI-aware bean.
• Image Changes: UBI 9 is now the default image instead of UBI 8. Builder images use UBI 9, and runtime images have different base images for JVM and native modes.
• Mockito Strategy: The quarkus-junit5-mockito dependency now uses the inline strategy by default.
• Telemetry Extension: A new bridge allows pushing Micrometer metrics to OpenTelemetry. The quarkus-micrometer-opentelemetry extension can be added.
• Update Command: The Quarkus CLI can be used to update to the latest version with quarkus update.
• LTS and Micro Releases: Quarkus releases LTS versions every six months and micro releases without a schedule. From version 3.15.0, micro LTS releases will be every two months and only contain security and low-risk bug fixes. In case of a critical CVE, an emergency micro release is provided.