In the current release, CacheManagerInfoBuildItem moves from io.quarkus.cache.deployment.spi to io.quarkus.cache.deployment. This change affects only extension maintainers who integrate with the cache extension because build fail if your extension imports the SPI class.

Update your imports from io.quarkus.cache.deployment.spi.CacheManagerInfoBuildItem to io.quarkus.cache.deployment.CacheManagerInfoBuildItem.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.30: CacheManagerInfoBuildItem moved from SPI to the deployment module.

In the current release, reading quarkus.http.port, quarkus.http.test-port, or test.url with System.getProperty() no longer returns the resolved random port values. This change affects applications and tests that build URLs from these system properties because they now keep their original values. Read these values from the Quarkus Config system, or inject io.quarkus.vertx.http.HttpServer to get the effective HTTP server configuration.

For more information, see the following resources:

In the current release, when an extension consumes a MultiBuildItem in a @BuildStep, Quarkus returns an immutable List<BuildItem> instead of a mutable copy.

This affects extension code that sorts or otherwise modifies the returned list. Copy the list before modifying it, or use stream().sorted() when you only need sorted iteration.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.32: List<BuildItem> immutable.

In the current release, the lz4-java dependency switches from org.lz4:lz4-java to at.yawk.lz4:lz4-java. This change affects dependency resolution when your application or a dependency still pulls org.lz4:lz4-java because you can end up with conflicting LZ4-java artifacts on the classpath. Exclude org.lz4:lz4-java from your dependencies, then add at.yawk.lz4:lz4-java where needed.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.31: LZ4-java groupId change.

In the current release, Qute changes TemplateInstance so that all rendering methods throw TemplateException on failure. Previously, rendering methods could throw TemplateException or an arbitrary runtime exception, and some failures could lead to a timeout when the underlying async operation did not complete.

Now, Qute catches these failures and throws TemplateException with the original runtime exception set as the cause. Update your exception handling to catch TemplateException for TemplateInstance rendering methods and inspect the cause when needed.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.29: Qute.

In the current release, support for RHEL 8 is deprecated and planned to be removed in a future release.

To ensure continued support, migrate to RHEL 9.

For more information about migrating from RHEL 8, see Upgrading from RHEL 8 to RHEL 9.

In the current release, the Hibernate ORM extension fails fast when you deactivate a persistence unit with quarkus.hibernate-orm.active=false and the application still accesses Hibernate ORM CDI beans. This change causes startup failures for static CDI injection points, and it causes runtime exceptions for dynamic retrieval paths, instead of failing later on first access. Activate the persistence unit, or update your code to access Hibernate ORM beans only when the persistence unit is active, for example, by injecting Instance<Session> or InjectableInstance<Session>.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.29: Hibernate ORM inactive fail fast.

In the current release, the Hibernate ORM extension stays enabled even when the application defines no Hibernate or Jakarta Persistence entities. This changes behavior for applications that include the Hibernate ORM extension and configure a datasource because Hibernate ORM now starts instead of being disabled. Disable Hibernate ORM explicitly by setting quarkus.hibernate-orm.enabled=false if the application does not need Hibernate ORM.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.29: Hibernate ORM enabled even if no entities are defined.

In the current release, Hibernate Reactive fails fast when you deactivate a persistence unit, and the application still accesses Hibernate Reactive CDI beans such as Mutiny.SessionFactory. This change causes startup failures for static CDI injection points, and it causes runtime exceptions for dynamic retrieval paths, instead of failing later on first access. Activate the persistence unit, or update your code to access Hibernate Reactive beans only when the persistence unit is active, for example, by injecting InjectableInstance<Mutiny.SessionFactory>.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.29: Hibernate Reactive inactive fail fast.

In the current release, the Hibernate Reactive extension stays enabled even when the application defines no Hibernate Reactive entities. This changes behavior for applications that include the Hibernate Reactive extension and configure a reactive datasource because Hibernate Reactive now starts instead of being disabled. Disable Hibernate Reactive explicitly by setting quarkus.hibernate-reactive.enabled=false if the application does not need Hibernate Reactive.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.29: Hibernate Reactive enabled even no entities are defined.

In the current release, Hibernate Search fails fast when a persistence unit is deactivated, and the application continues to access Hibernate Search CDI beans such as SearchSession or SearchMapping. This change causes startup failures at static CDI injection points and runtime exceptions for dynamic retrieval paths, instead of allowing the application to start and fail on first access. Update your code to access Hibernate Search beans only when the persistence unit is active, for example, by injecting InjectableInstance<SearchSession> or InjectableInstance<SearchMapping>.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.29: Hibernate Search inactive fail fast.

In the current release, the defaults for the Hibernate Search Elasticsearch client connection limits have changed. This change can increase the number of connections opened to your Elasticsearch cluster if you relied on the previous defaults. Set the following properties to keep the previous defaults:

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.29: Hibernate Search Elasticsearch client defaults.

In the current release, Agroal removes support for Apache Derby. Applications that connect to Apache Derby with the Agroal JDBC datasource fail to build because the Maven dependency no longer exists.

Replace Apache Derby with a supported database, or set db-kind=other to use an unsupported database driver. When you set db-kind=other, native compilation does not work, and other limitations can apply.

For more information, see the following resources:

In the current release, Agroal changes the default maximum pool size from 20 to 50. This change can increase the number of database connections opened by default when you do not set quarkus.datasource.jdbc.max-size. Set quarkus.datasource.jdbc.max-size=20 to keep the previous default, or set a value that matches your database capacity and workload.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.31: Agroal and JDBC.

In the current release, the datasource Dev Services implementation uses the new Dev Services model, which changes the io.quarkus.datasource.deployment.spi SPI. This change affects extension developers only. Extensions that produce DevServicesDatasourceProviderBuildItem can fail to build until you update them to the new SPI.

Update your extension to use the new datasource Dev Services model. For an example migration, see the MS SQL conversion.

For more information, see the following resources:

In the current release, Apicurio Registry is upgraded from version 2 to version 3. The Apicurio Registry extensions quarkus-apicurio-registry-avro and quarkus-apicurio-registry-json-schema now use Apicurio Registry 3.x client libraries.

This major version upgrade introduces the following breaking changes:

In the current release, the deprecated quarkus.datasource.jdbc.enable-metrics configuration property is removed. Applications that set this property no longer control Agroal JDBC Micrometer metrics with it. Replace quarkus.datasource.jdbc.enable-metrics with quarkus.datasource.jdbc.metrics.enabled.

For more information, see the following resources:

In the current release, the OpenTelemetry (OTel) Software Development Kit (SDK) is updated to 1.49.0. This change renames OTel semantic-convention attribute keys, including those that affect SmallRye Reactive Messaging telemetry. Update queries, dashboards, and alert rules to use the new attribute keys.

Impacted attributes include:

The migration guide also lists deprecated attributes that are scheduled for replacement. Plan updates for these attributes now to avoid future migration work.

Deprecated attributes include:

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.30: OpenTelemetry breaking changes.

In the current release, the OpenTelemetry (OTel) extension fixes a typo in the package name io.quarkus.opentelemetry.runtime.tracing.intrumentation by renaming it to io.quarkus.opentelemetry.runtime.tracing.instrumentation. This change breaks builds for applications that import classes from the old package name. Update your imports to the new package name.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.31: Package name typo fixed in the OpenTelemetry extension.

In the current release, Elytron Security Properties File raises password-hashing standards by changing the default hash algorithm from md5 to sha512. This change affects authentication when your properties file contains md5 hashed passwords because Elytron no longer matches them with the new default algorithm. Set the hash algorithm explicitly, or rehash stored passwords with sha512.

For more information, see the following resources:

In the current release, the TLS registry enables only TLSv1.3 by default. This change raises the default security level, but it can cause TLS handshake failures when a peer requires TLSv1.2 or earlier. If you need to accept TLSv1.2, set quarkus.tls.protocols or quarkus.tls.<name>.protocols to include it, for example, TLSv1.3, TLSv1.2. TLSv1.2 is not deprecated, but TLSv1.3 remains the recommended protocol for stronger security.

For more information, see the following resources:

In the current release, security CDI interceptors run before transaction interceptors to avoid allocating transaction resources before a security check succeeds. This change affects code paths where authorization checks expect an active transaction started by an endpoint method interceptor. Start the transaction in the authorization check code path, or move transactional work to execute after authorization succeeds.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.31: Security interceptors run before transaction interceptors.

In the current release, ahead-of-time (AOT) cache generation requires Java 25. This change causes AOT cache generation to fail when you run it with an earlier Java version. Run AOT cache generation with Java 25, or disable AOT cache generation if you cannot move to Java 25 for this step.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.30: AOT.

In the current release, Dev Services updated the default Elasticsearch image from 9.1 to 9.2 and the default OpenSearch image from 3.1 to 3.3. This change affects development and test environments that rely on the default images, as the updated containers might alter server behavior and compatibility. Set an explicit image name to keep a specific Elasticsearch or OpenSearch version in your Dev Services setup.

For more information, see the following resources:

In the current release, Maven projects can set <packaging>quarkus</packaging> to use a Quarkus-specific build lifecycle. When you switch to quarkus packaging, Maven no longer runs maven-jar-plugin, so Maven no longer builds the default jar artifact. When you switch to quarkus packaging, Maven also no longer runs the default maven-install-plugin and maven-deploy-plugin executions for that default jar artifact. Keep <packaging>jar</packaging> if you rely on the default jar artifact, or configure explicit install and deploy steps for the artifact you want to publish. Set quarkus packaging only in the application module, not in library modules.

For more information, see the following resources:

In the current release, the default native builder image now uses registry.access.redhat.com/quarkus/mandrel-25-rhel9:25.0, which replaces the previous RHEL 8-based Mandrel builder image. This affects container-based native builds that still use UBI 8 runtime images, because native executables built with a UBI 9-based builder image are not compatible with UBI 8 base images.

Update the runtime image to a UBI 9-based image.

If you build your native application on a FIPS-enabled system, the resulting native image will have a dependency on the java-25-openjdk-crypto-adapter RHEL 9 package. Therefore, if you deploy native applications on FIPS-enabled RHEL 9 systems, install java-25-openjdk-crypto-adapter in the target image. This requirement applies only to FIPS-enabled native deployments.

The automatic update process does not cover this change. Apply this update manually.

For more information, see the following resources:

In the current release, the test framework is upgraded from JUnit 5 to JUnit 6. To avoid confusion, Quarkus renames the *-junit5 test artifacts to *-junit.

Run quarkus update to apply the dependency relocations automatically. If you do not run quarkus update, update your dependencies to the new artifact names:

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.31: JUnit 6.

In the current release, the Testcontainers dependency has been updated to Version 2.0. This change affects projects that reference Testcontainers artifacts or packages directly because some artifact and package names have changed. Run quarkus update to apply the dependency and artifact renames automatically, then adjust any remaining direct Testcontainers references in your build and code.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.31: Testcontainers 2.

In the current release, projects that run tests on Java 25 need an updated Maven Surefire and Failsafe argLine configuration to avoid JVM warnings.

If your pom.xml defines an explicit <argLine>, prepend @{argLine} to the existing <argLine> so the build automatically includes the required JVM arguments.

If your pom.xml does not define <argLine>, add <argLine>@{argLine}</argLine> so future test JVM tuning does not drop the required arguments.

Verify that the Quarkus Maven Plugin configuration includes <extensions>true</extensions>.

For more information, see the following resources:

In the current release, builds that set quarkus.http.cors fail to enable the CORS filter because this configuration key is removed. Update your configuration to use quarkus.http.cors.enabled instead.

For more information, see the Quarkus Content from github.com is not included.Migration guide 3.28.

In the current release, the SmallRye GraphQL client extension removes the deprecated quarkus.smallrye-graphql.client.<client-name>.key-store.* and quarkus.smallrye-graphql.client.<client-name>.trust-store.* properties for Transport Layer Security (TLS) configuration.

Applications that relied on these properties no longer apply TLS settings for GraphQL clients. Configure TLS with the TLS registry, then reference that TLS configuration from your GraphQL clients.

For more information, see the following resources: