3.9.0.CR2

[gsmet]

Branch

3.9

Qualifier

CR2

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

We are going to release the following release:

• Quarkus 3.9.0.CR2
• On branch 3.9
• With Java 17
• This is a preview release (e.g. Alpha, Beta, CR).

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

If not, simply close this issue.

---

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 - [ ] 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 - [ ] Announce release

[github-actions[bot]]

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

:bulb: 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[bot]]

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

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.

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.9.0.CR2/ 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 - [ ] 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 - [ ] Announce release

[github-actions[bot]]

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

[github-actions[bot]]

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

:bulb: In the case of preview releases (e.g. Alpha1, CR1...), the release will be built from the main branch

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

cd <your quarkus-platform clone>
git checkout main
git pull upstream main
git checkout -b quarkus-3.9.0.CR2
./update-quarkus-version.sh 3.9.0.CR2

• Check the diff with git diff

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

• 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
• Make sure you have merged all the pull requests that should be included in this version of the Platform

Once everything has been merged to branch main, 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 - [ ] 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 - [ ] Announce release

[github-actions[bot]]

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

[github-actions[bot]]

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

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.

:bulb: 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.9.0.CR2/ 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 - [ ] 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 - [ ] Announce release

[github-actions[bot]]

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

[github-actions[bot]]

:white_check_mark: 3.9.0.CR2 was successfully released.

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

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

./trigger-performance-testing.sh 3.9.0.CR2

to trigger the performance evaluation testing for this release.

Then it is time to send an email to quarkus-dev@googlegroups.com:

Subject:

Quarkus 3.9.0.CR2 released

Body:

Hi,

We released Quarkus 3.9.0.CR2.

Changelog is here:
https://github.com/quarkusio/quarkus/releases/tag/3.9.0.CR2

Please try to upgrade your applications and report back:
- if everything is going well, just post a reply to this thread
- if you encounter issues, please open a GitHub issue in our tracker with a simple reproducer

We will build the final core artifacts next Wednesday.

Thanks!

--
The Quarkus dev team