Quarkus 3.38.3 has been released as a maintenance update for the 3.38 release train, containing bugfixes and documentation improvements. It is described as a safe upgrade for anyone already on 3.38. Users are encouraged to update via the Quarkus CLI using the quarkus update command, which can migrate applications from any prior version, including 2.x, to 3.38. A migration guide and full GitHub changelog are linked for further details.
Questions this post answers
Is Quarkus 3.38.3 a safe upgrade from Quarkus 3.38?
Yes, Quarkus 3.38.3 is a maintenance release for the 3.38 release train containing only bugfixes and documentation improvements, making it a safe upgrade for anyone already running 3.38. To update, use the Quarkus CLI and run the quarkus update command, which works even when migrating from Quarkus 2.x. Track Quarkus maintenance releases like this on daily.dev before rolling out an upgrade.