A week after Alpha5, we are releasing Quarkus 3.0.0.Alpha6. While Alpha5 came with major changes such as the upgrade to Hibernate ORM 6, Alpha6 is a smaller release packed with bugfixes, enhancements, and improvements to our upgrade process.


Among all the bugfixes and enhancements, two are worth mentioning in particular:

  • Enabling OpenTelemetry for JDBC is now as simple as setting quarkus.datasource.jdbc.telemetry to true

  • CredentialsProviders are now supported for MongoDB connections

The upgrade progress (presented below) was also improved and it will now:

  • Upgrade your Quarkiverse extensions to versions supporting Quarkus 3 (when they are available)

  • Replace more deprecated classes and annotations

  • Replace some deprecated configuration properties with the new ones

If you encounter issues with this version or the upgrade, please open issues in our tracker!

Trying out Quarkus 3

For now the easiest way to get started is using code.quarkus.io or use the Quarkus CLI:

quarkus create app --stream=3.0

Mind you that at this stage, while all the core extensions are available, only parts of the Quarkus platform is present. Not all extensions have yet migrated to Jakarta packages (e.g. Camel Quarkus or Kogito are not yet available).

Upgrading to Quarkus 3

For existing applications where all extensions are available, we have an OpenRewrite recipe that you can try.

There is a one-liner that attempts to do it automatically using a JBang script.

If you have JBang already installed, run:

jbang --fresh upgrade-to-quarkus3@quarkusio

If not, for Linux and macOS:

curl -Ls https://sh.jbang.dev | bash -s - --fresh upgrade-to-quarkus3@quarkusio

and for Windows:

iex "& { $(iwr https://ps.jbang.dev) } --fresh upgrade-to-quarkus3@quarkusio"

Once this has been run your project should have its dependencies, source code and documentation updated to use Quarkus 3.

If it does not work for you, it could be we missed something or you are using extensions not yet supporting Quarkus 3.

Let us know in either case so we can together improve the migration script.