The newest release for Quarkus, version 1.3.0.Final, has arrived. Explore the newest changes and see how the Quarkus Java framework helps Java fit in with the cloud native world. Let’s take a closer look at the changelog and see what’s new.

Another update for Quarkus has arrived; meet version 1.3.0.Final. While 1.3.0.Final does not bring any major changes to the framework, it does update plenty of its infrastructure.

The long list of bug changes, minor updates, and documentation upgrades polishes Quarkus to a shine.

What is Quarkus? According to its homepage, it is a “Kubernetes Native Java stack tailored for OpenJDK HotSpot and GraalVM, crafted from the best of breed Java libraries and standards”. Even better, it is entirely open source, so let’s take a look.

1.3.0.Final changes
This is the final update for Quarkus 1.3.0, so with this arrival, 1.3.0 is now officially complete.

Some of the newest changes include:

Quarkus now generates entities in the correct class loader, fixing a previous issue.
Documentation changes: A number of typos have been corrected, links have been fixed, and some clarification added for a smoother learning experience.
Fixed windows failures
Maven project fixes
Users can now skip the build mojo from the command line.
Added new section on reactive security
https:// for Maven xsd will now be used
Added a Hibernate ORM hot reload test
Various upgrades: Updated to smallrye-jwt-2.1.1, proton-j to 0.33.3, postgresql from 42.2.10 to 42.2.11, OptaPlanner from 7.33.0 to 7.34.0, and Gradle to 6.2.2,
Security tests and fixes
That’s not all, so be sure to read the entire changelog and see what minor changes and bug fixes have been made.