Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

3.14.1 #87

Closed
1 task
gsmet opened this issue Aug 28, 2024 · 21 comments
Closed
1 task

3.14.1 #87

gsmet opened this issue Aug 28, 2024 · 21 comments

Comments

@gsmet
Copy link
Contributor

gsmet commented Aug 28, 2024 •
edited by github-actions bot
Loading

Branch

3.14

Qualifier

No response

Origin branch

No response

Major version

  • This release is a major version.
@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Prerequisites

You can follow the progress of the workflow here.

@github-actions GitHub Actions
Copy link

🙌 We are going to release the following release:

  • Quarkus 3.14.1
  • On branch 3.14
  • With Java 17
  • 💡 We detected that this 3.14.1 release will be the first final as 3.14.0 has not been fully released

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
Copy link
Contributor Author

gsmet commented Aug 28, 2024

@quarkusbot yes

@github-actions GitHub Actions
Copy link

⚙️ 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 GitHub Actions
Copy link

✅ 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 GitHub Actions
Copy link

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

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
Copy link
Collaborator

@quarkusbot continue

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

@github-actions GitHub Actions
Copy link

⚙️ 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 GitHub Actions
Copy link

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

@github-actions GitHub Actions
Copy link

🙌 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 main
git pull upstream main
git checkout -b quarkus-3.14.1
./update-quarkus-version.sh 3.14.1
  • Check the diff with git diff
git add .
git commit -m 'Upgrade to Quarkus 3.14.1'
git push origin quarkus-3.14.1

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.

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
Copy link
Contributor Author

gsmet commented Aug 28, 2024

@quarkusbot continue

@github-actions GitHub Actions
Copy link

⚙️ 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 GitHub Actions
Copy link

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

@github-actions GitHub Actions
Copy link

Caution

An error occurred while executing step Release the Quarkus Platform.

Note

Please check the workflow run logs but there is a good chance that the issue was due to a problem with accessing s01.oss.sonatype.org either when authenticating or when uploading the artifacts.
If so, please retry.

Status page for s01.oss.sonatype.org: https://status.maven.org/.

You can find more information about the failure in the workflow run logs.

Important

This is not a fatal error, you can retry by adding a @quarkusbot retry 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 ⚙️ ☚ You are here
  • 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
Copy link
Contributor Author

gsmet commented Aug 28, 2024

@quarkusbot retry

@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Release 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
  • Release the Quarkus Platform ⚙️ ☚ You are here
  • 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 GitHub Actions
Copy link

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

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
Copy link
Collaborator

@quarkusbot continue

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

@github-actions GitHub Actions
Copy link

⚙️ 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 GitHub Actions
Copy link

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

@github-actions GitHub Actions
Copy link

✅ 3.14.1 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.14.1

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)
    • If a Mandrel/GraalVM upgrade is necessary, make sure it is prominent in the announcement* 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.

Newsworthy changes (in Asciidoc)

* https://github.com/quarkusio/quarkus/pull/37034[#37034] - Decorate stacktraces in dev mode error page
* https://github.com/quarkusio/quarkus/pull/40329[#40329] - Speedup Hibernate ORM's enhancement of large models
* https://github.com/quarkusio/quarkus/pull/41063[#41063] - Generate faster reflection-free Jackson serializers
* https://github.com/quarkusio/quarkus/pull/41249[#41249] - Initial gRPC CLI
* https://github.com/quarkusio/quarkus/pull/41359[#41359] - Upgrade to Hibernate ORM 6.6 / Search 7.2 / Reactive 2.4
* https://github.com/quarkusio/quarkus/pull/41648[#41648] - Make mvnd 1.X work and require Maven 3.9.6 to build Quarkus
* https://github.com/quarkusio/quarkus/pull/42097[#42097] - Update UBI images to 1.20/8.10
* https://github.com/quarkusio/quarkus/pull/42105[#42105] - Let's Encrypt Support
* https://github.com/quarkusio/quarkus/pull/42141[#42141] - Reimplement the extension annotation processor
* https://github.com/quarkusio/quarkus/pull/42409[#42409] - Vertx HTTP: execute custom logic when HTTP server is started
* https://github.com/quarkusio/quarkus/pull/42445[#42445] - Upgrade mongodb-client to 5.1.3
* https://github.com/quarkusio/quarkus/pull/42519[#42519] - Accept signed OIDC UserInfo

Other breaking changes (FYI, in Asciidoc)

* https://github.com/quarkusio/quarkus/pull/42444[#42444] - Fix consistency of SmallRye Health config roots

Announcement email template

Subject:

[RELEASE] Quarkus 3.14.1

Body:

Hello,

Quarkus 3.14.1 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-14-1-released/.

* Major changes:

  * [#37034] Decorate stacktraces in dev mode error page
  * [#40329] Speedup Hibernate ORM's enhancement of large models
  * [#41063] Generate faster reflection-free Jackson serializers
  * [#41249] Initial gRPC CLI
  * [#41359] Upgrade to Hibernate ORM 6.6 / Search 7.2 / Reactive 2.4
  * [#41648] Make mvnd 1.X work and require Maven 3.9.6 to build Quarkus
  * [#42097] Update UBI images to 1.20/8.10
  * [#42105] Let's Encrypt Support
  * [#42141] Reimplement the extension annotation processor
  * [#42409] Vertx HTTP: execute custom logic when HTTP server is started
  * [#42445] Upgrade mongodb-client to 5.1.3
  * [#42519] Accept signed OIDC UserInfo

* BOM dependency:

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

* Changelogs are available from https://github.com/quarkusio/quarkus/releases/tag/3.14.0.CR1, https://github.com/quarkusio/quarkus/releases/tag/3.14.0, and https://github.com/quarkusio/quarkus/releases/tag/3.14.1
* Download is available from https://github.com/quarkusio/quarkus/releases/tag/3.14.1
* Documentation: https://quarkus.io

--
The Quarkus dev team

For new major/minor releases, we include the list of contributors in the announcement blog post.
The number of contributors can be found in the Contributors section of the project home page.
You can get a rough list of contributors (check for duplicates!) since the previous minor by executing the following commands in a Quarkus repository local clone:

git fetch upstream --tags
git shortlog -s '3.13.0'..'3.14.1' | cut -d$'\t' -f 2 | grep -v dependabot | grep -v quarkusbot | sort -d -f -i | paste -sd ',' - | sed 's/,/, /g'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gsmet @quarkusbot and others