3.6.2

[gsmet]

Branch

3.6

Qualifier

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.

Where am I?

- [ ] Prerequisites :gear: ☚ You are here - [ ] 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 - [ ] Release the Quarkus Platform - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update documentation - [ ] Announce release

[github-actions[bot]]

We are going to release the following release:

• 3.6.2

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

If not, simply close this issue.

[gsmet]

@quarkusbot yes

[github-actions[bot]]

:gear: Proceeding to step Prepare the core release

You can follow the progress of the workflow here.

Where am I?

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

[github-actions[bot]]

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:

• Wait for one hour
• Check that https://repo1.maven.org/maven2/io/quarkus/quarkus-core/3.6.2/ does not return a 404

Once these two conditions are met, you can continue with the release by adding a @quarkusbot continue comment.

(Note that we plan to automate this step soonish)

[gsmet]

@quarkusbot continue

[github-actions[bot]]

:gear: Proceeding to step Release Gradle plugin

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 - [ ] Release Gradle plugin :gear: ☚ You are here - [ ] Execute post-core-release operations - [ ] Release the Quarkus Platform - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update documentation - [ ] Announce release

[github-actions[bot]]

Now is time to release the Quarkus Platform. This is a manual process:

• Make sure you have merged all the pull requests that should be included in this version of the Platform
• Then follow (roughly) this process:

cd <your quarkus-platform clone>
git checkout 3.6
git pull upstream 3.6
git checkout -b quarkus-3.6.2
./update-quarkus-version.sh 3.6.2

• Check the diff with git diff

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

• Create a pull request for branch 3.6

• Wait for CI to go green

• Merge the pull request

  git checkout 3.6
  git pull upstream 3.6

• Then actually release the version with the following line:

TAG=3.6.2 && ./check-version.sh $TAG && ./mvnw release:prepare release:perform -DdevelopmentVersion=999-SNAPSHOT -DreleaseVersion=$TAG -Dtag=$TAG -DperformRelease -Prelease,releaseNexus -DskipTests -Darguments=-DskipTests

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

• Wait for 40 minutes
• Check that https://repo1.maven.org/maven2/io/quarkus/platform/quarkus-bom/3.6.2/ does not return a 404

Once these two conditions are met, you can continue with the release by adding a @quarkusbot continue comment.

[gsmet]

@quarkusbot continue

[github-actions[bot]]

:gear: Proceeding to step Update extension catalog

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] Release the Quarkus Platform - [ ] Update extension catalog :gear: ☚ You are here - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update documentation - [ ] Announce release

[github-actions[bot]]

:white_check_mark: 3.6.2 was successfully released.

Time to write the announcement:

• Update the versions 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
• Send the announcement to quarkus-dev@googlegroups.com
• Send the announcement to various social networks using https://buffer.com/

Here is some content that could help in writing the announcement:

Announcement email template

Subject: [RELEASE] Quarkus 3.6.2

Hello,

Quarkus 3.6.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-6-2-released/.

* BOM dependency:

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

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

The Quarkus dev team