3.14.0

[gsmet]

Branch

3.14

Qualifier

No response

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.14.0
• On branch 3.14
• With Java 17

Important

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 2 hours and 30 minutes 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.14.0/ 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.

Warning

This is the .0 release so we update the Platform first then wait one week for the Platform members to contribute their updates then we release. Make sure you follow the instructions closely.

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 main
git pull upstream main
git checkout -b quarkus-3.14.0
./update-quarkus-version.sh 3.14.0

• Check the diff with git diff

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

• Create a pull request targeting branch main (or generic link if targeted link doesn't work)
• Wait for CI to go green
• Merge the pull request
• Send an email to the Platform coordination mailing list: quarkus-platform-coordination@googlegroups.com :

Subject:

Quarkus 3.14.0 core artifacts are available

Body:

Hi,

The Quarkus 3.14.0 core artifacts are available on Maven Central.

The pull request updating the Platform to Quarkus 3.14.0 has been merged in the main branch.
We pinged the team maintaining components not passing the tests in the pull request.

If you want to update your components, please create your pull requests and make sure they are merged before next Tuesday.

Thanks.

--
The Quarkus dev team

• If CI failed for some Platform members, please contact them so that they are aware of the issues

Warning

IMPORTANT - STOP HERE
IMPORTANT - Wait a week before continuing with the Platform release

• Make sure you have merged all the pull requests that should be included in this version of the Platform
• Once all the pull requests are merged, create the branch:

git checkout main
git pull upstream main
git checkout -b 3.14
git push upstream 3.14

Important

Once everything has been pushed to branch 3.14, you can continue with the release by adding a @quarkusbot continue comment.

---

If you have to release 3.14.1 right away as the first Platform release

This can happen if, for instance, an important regression is detected just after the 3.14.0 core release and before the Platform release.
It might also happen if you want to fix a CVE before releasing the Platform.

In this case, just close this release issue and start a new release for the 3.14.1 release as usual.
The instructions will be automatically adapted.

---

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