3.19.3

[gsmet]

Branch

3.19

Qualifier

No response

Emergency release

• [ ] This release is an emergency release.

Origin branch

No response

Major version

• [ ] This release is a major version.

[github-actions[bot]]

:gear: Proceeding to step Prerequisites

You can follow the progress of the workflow here.

[github-actions[bot]]

:raised_hands: We are going to release the following release:

• Quarkus 3.19.3
• On branch 3.19
• With Java 17

[!IMPORTANT] Make sure you have merged all the backport pull requests in the 3.19 branch.

Please approve with a @quarkusbot yes comment if you want to continue with the release.

If not, simply close this issue.

---

Legend for the admonitions

> [!IMPORTANT] > A manual confirmation/intervention is needed. > [!TIP] > Some useful information about the release process. > [!NOTE] > Some additional information. > [!WARNING] > Something important to consider. > [!CAUTION] > An error occurred.

---

Where am I?

- [X] Prerequisites - [ ] Approve the core release :pause_button: ☚ You are here - [ ] Prepare the core release - [ ] Perform the core release - [ ] Sync core release to Maven Central - [ ] Release Gradle plugin - [ ] Execute post-core-release operations - [ ] Prepare the Quarkus Platform - [ ] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[gsmet]

@quarkusbot yes

[github-actions[bot]]

:gear: Proceeding to step Approve the core release

You can follow the progress of the workflow here.

---

Where am I?

- [X] Prerequisites - [ ] Approve the core release :gear: ☚ You are here - [ ] Prepare the core release - [ ] Perform the core release - [ ] Sync core release to Maven Central - [ ] Release Gradle plugin - [ ] Execute post-core-release operations - [ ] Prepare the Quarkus Platform - [ ] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[github-actions[bot]]

:white_check_mark: Core release is approved, proceeding...

[!TIP] The Core release steps take approximately 3 hours so don't panic if it takes time. You will receive feedback in this very issue when further input is needed or if an error occurs.

[github-actions[bot]]

:white_check_mark: The core artifacts have been pushed to s01.oss.sonatype.org.

[!WARNING] IMPORTANT You need to wait for them to be synced to Maven Central before continuing with the release.

The publication of the core artifacts will take 60-80 minutes.

[!TIP] We started a separate workflow to monitor the situation for you. It will automatically continue the release process once it detects the artifacts have been synced to Maven Central.

---

If things go south

If things go south, you can monitor the situation manually: * Wait for 1 hour (starting from the time of this comment) * Check that https://repo1.maven.org/maven2/io/quarkus/quarkus-bom/3.19.3/ does not return a 404 Once these two conditions are met, you can continue with the release by adding a `@quarkusbot continue` comment.

---

Where am I?

- [X] Prerequisites - [X] Approve the core release - [X] Prepare the core release - [X] Perform the core release - [ ] Sync core release to Maven Central :pause_button: ☚ You are here - [ ] Release Gradle plugin - [ ] Execute post-core-release operations - [ ] Prepare the Quarkus Platform - [ ] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[quarkusbot]

@quarkusbot continue

:white_check_mark: We have detected that the core artifacts have been synced to Maven Central.

[github-actions[bot]]

:gear: Proceeding to step Sync core release to Maven Central

You can follow the progress of the workflow here.

---

Where am I?

- [X] Prerequisites - [X] Approve the core release - [X] Prepare the core release - [X] Perform the core release - [ ] Sync core release to Maven Central :gear: ☚ You are here - [ ] Release Gradle plugin - [ ] Execute post-core-release operations - [ ] Prepare the Quarkus Platform - [ ] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[github-actions[bot]]

:white_check_mark: Core artifacts have been synced to Maven Central, continuing...

[github-actions[bot]]

:raised_hands: Now is time to update Quarkus in the Quarkus Platform. This is a manual process.

[!IMPORTANT] First, you need to update the Platform locally, create a pull request, wait for CI and merge it.

You can find detailed instructions below.

• Go into your Quarkus Platform clone directory:

cd <your quarkus-platform clone>

• Follow (roughly) these steps (upstream is the upstream repository, origin is your fork):

git checkout 3.19
git pull upstream 3.19
git checkout -b quarkus-3.19.3
./update-quarkus-version.sh 3.19.3

• Check the diff with git diff
• Then:

git add .
git commit -m 'Upgrade to Quarkus 3.19.3'
git push origin quarkus-3.19.3

• Create a pull request targeting branch 3.19 (or generic link if targeted link doesn't work)
• Wait for CI to go green
• Merge the pull request
• Make sure you have merged all the pull requests that should be included in this version of the Platform

[!IMPORTANT] Once everything has been merged to branch 3.19, you can continue with the release by adding a @quarkusbot continue comment.

---

Where am I?

- [X] Prerequisites - [X] Approve the core release - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [ ] Prepare the Quarkus Platform :pause_button: ☚ You are here - [ ] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[gsmet]

@quarkusbot continue

[github-actions[bot]]

:gear: Proceeding to step Prepare the Quarkus Platform

You can follow the progress of the workflow here.

---

Where am I?

- [X] Prerequisites - [X] Approve the core release - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [ ] Prepare the Quarkus Platform :gear: ☚ You are here - [ ] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[github-actions[bot]]

:white_check_mark: The Platform branch 3.19 is ready to be released, continuing...

[github-actions[bot]]

:white_check_mark: The Platform artifacts have been pushed to s01.oss.sonatype.org.

[!WARNING] IMPORTANT You need to wait for them to be synced to Maven Central before continuing with the release:

The publication of the Platform artifacts will take 20-40 minutes.

[!TIP] We started a separate workflow to monitor the situation for you. It will automatically continue the release process once it detects the artifacts have been synced to Maven Central.

---

If things go south

If things go south, you can monitor the situation manually: * Wait for 40 minutes (starting from the time of this comment) * Check that https://repo1.maven.org/maven2/io/quarkus/platform/quarkus-bom/3.19.3/ does not return a 404 Once these two conditions are met, you can continue with the release by adding a `@quarkusbot continue` comment.

---

Where am I?

- [X] Prerequisites - [X] Approve the core release - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [X] Prepare the Quarkus Platform - [X] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central :pause_button: ☚ You are here - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[quarkusbot]

@quarkusbot continue

:white_check_mark: We have detected that the Platform artifacts have been synced to Maven Central.

[github-actions[bot]]

:gear: Proceeding to step Sync Platform release to Maven Central

You can follow the progress of the workflow here.

---

Where am I?

- [X] Prerequisites - [X] Approve the core release - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [X] Prepare the Quarkus Platform - [X] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central :gear: ☚ You are here - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

[github-actions[bot]]

:white_check_mark: Platform artifacts have been synced to Maven Central, continuing...

[github-actions[bot]]

:white_check_mark: 3.19.3 was successfully released.

:raised_hands: Some manual steps are required to finalize the release.

[!IMPORTANT] You need to:

• Trigger the performance testing (we can't automate it for now for security reasons)
• Announce the release on quarkus-dev@ and on social networks

You can find detailed instructions below.

Trigger performance testing

Connected to the Red Hat VPN, in a clone of https://github.com/quarkusio/quarkus-release, run:

./trigger-performance-testing.sh 3.19.3

to trigger the performance evaluation testing for this release.

Announce release

Then it is time to announce the release:

• Update the versions of the website in _data/versions.yaml
• Write a blog post for the website
  • Use a previous announcement as a template (be aware, annoucements are very different for the first final of a major/minor and the follow-up micros)
• Push it and wait for it to be live on quarkus.io - you can follow the progress of the deployment on GitHub Actions
• Send the announcement to quarkus-dev@googlegroups.com
• Send the announcement to various social networks using https://buffer.com/

You can find below a template that can help you with writing the announcement email.

Announcement email template

Subject:

[RELEASE] Quarkus 3.19.3

Body:

Hello,

Quarkus 3.19.3 has been released, and is now available from the Maven Central repository. The quickstarts and documentation have also been updated.

More information in the announcement blog post: https://quarkus.io/blog/quarkus-3-19-3-released/.

* BOM dependency:

  <dependency>
      <groupId>io.quarkus.platform</groupId>
      <artifactId>quarkus-bom</artifactId>
      <version>3.19.3</version>
      <type>pom</type>
      <scope>import</scope>
  </dependency>

* Changelog and download are available from https://github.com/quarkusio/quarkus/releases/tag/3.19.3
* Documentation: https://quarkus.io

--
The Quarkus dev team