Quarkus 3.3.1 released - Maintenance release
We released Quarkus 3.3.1, our first maintenance release for our 3.3 release train.
It includes a bunch of bugfixes, together with documentation improvements.
We are aware of a startup performance/memory regression introduced in 3.3 and are working hard on fixing it. This issue is not solved in 3.3.1 but should be solved in the upcoming 3.3.2 that will be released next week.
Update
To update to Quarkus 3.3.1, we recommend updating to the latest version of the Quarkus CLI and run:
quarkus updateTo migrate from 3.2, please refer to our migration guide.
If you are not already using 3.x, please refer to the 3.0 announcement for all the details. You can also refer to this blog post for additional details. Once you upgraded to 3.0, also have a look at the 3.1 and 3.2 migration guides.
Full changelog
You can get the full changelog of 3.3.1 on GitHub.
Come Join Us
We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together!
If you are a Quarkus user or just curious, don’t be shy and join our welcoming community:
-
provide feedback on GitHub;
-
craft some code and push a PR;
-
discuss with us on Zulip and on the mailing list;
-
ask your questions on Stack Overflow.
