3.18.2

[gsmet]

Branch

3.18

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]

⚙️ Proceeding to step Prerequisites

You can follow the progress of the workflow here.

[github-actions]

🙌 We are going to release the following release:

• Quarkus 3.18.2
• On branch 3.18
• With Java 17

Important

Make sure you have merged all the backport pull requests in the 3.18 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?

• Prerequisites
• Approve the core release ⏸️ ☚ 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]

⚙️ Proceeding to step Approve the core release

You can follow the progress of the workflow here.

---

Where am I?

• Prerequisites
• Approve the core release ⚙️ ☚ 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]

✅ 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]

✅ 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.18.2/ 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?

• Prerequisites
• Approve the core release
• Prepare the core release
• Perform the core release
• Sync core release to Maven Central ⏸️ ☚ 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

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

[github-actions]

⚙️ Proceeding to step Sync core release to Maven Central

You can follow the progress of the workflow here.

---

Where am I?

• Prerequisites
• Approve the core release
• Prepare the core release
• Perform the core release
• Sync core release to Maven Central ⚙️ ☚ 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]

✅ Core artifacts have been synced to Maven Central, continuing...

[github-actions]

🙌 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.18
git pull upstream 3.18
git checkout -b quarkus-3.18.2
./update-quarkus-version.sh 3.18.2

• Check the diff with git diff
• Then:

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

• Create a pull request targeting branch 3.18 (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.18, you can continue with the release by adding a @quarkusbot continue comment.

---

Where am I?

• Prerequisites
• Approve the core release
• 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 ⏸️ ☚ 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]

⚙️ Proceeding to step Prepare the Quarkus Platform

You can follow the progress of the workflow here.

---

Where am I?

• Prerequisites
• Approve the core release
• 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 ⚙️ ☚ 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]

✅ The Platform branch 3.18 is ready to be released, continuing...

[github-actions]

✅ 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.18.2/ 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?

• Prerequisites
• Approve the core release
• 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 ⏸️ ☚ 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

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

[github-actions]

⚙️ Proceeding to step Sync Platform release to Maven Central

You can follow the progress of the workflow here.

---

Where am I?

• Prerequisites
• Approve the core release
• 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 ⚙️ ☚ 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]

✅ Platform artifacts have been synced to Maven Central, continuing...

[github-actions]

✅ 3.18.2 was successfully released.

🙌 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.18.2

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 [email protected]
• 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.

Other breaking changes (FYI, in Asciidoc)

* https://github.com/quarkusio/quarkus/pull/45877[#45877] - Replace the id label with a name label for Netty allocator
* https://github.com/quarkusio/quarkus/pull/45950[#45950] - Correctly handle REST field injection

Announcement email template

Subject:

[RELEASE] Quarkus 3.18.2

Body:

Hello,

Quarkus 3.18.2 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-18-2-released/.

* BOM dependency:

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

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

--
The Quarkus dev team