3.13.0 - Githubissues

gsmet commented 1 month ago

Branch

3.13

Origin branch

No response

Qualifier

No response

Major version

[ ] This release is a major version.

github-actions[bot] commented 1 month ago

:gear: Proceeding to step Prerequisites

You can follow the progress of the workflow here.

github-actions[bot] commented 1 month ago

:raised_hands: We are going to release the following release:

Quarkus 3.13.0
On branch 3.13
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.

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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

gsmet commented 1 month ago

@quarkusbot yes

github-actions[bot] commented 1 month ago

: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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

github-actions[bot] commented 1 month ago

:white_check_mark: 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[bot] commented 1 month ago

:white_check_mark: 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.13.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?

- [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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

quarkusbot commented 1 month ago

@quarkusbot continue

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

github-actions[bot] commented 1 month ago

: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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

github-actions[bot] commented 1 month ago

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

github-actions[bot] commented 1 month ago

:raised_hands: 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.

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.13.0
./update-quarkus-version.sh 3.13.0

Check the diff with git diff

git add .
git commit -m 'Upgrade to Quarkus 3.13.0'
git push origin quarkus-3.13.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.13.0 core artifacts are available

Body:

Hi,

The Quarkus 3.13.0 core artifacts are available on Maven Central.

The pull request updating the Platform to Quarkus 3.13.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.13
git push upstream 3.13

[!IMPORTANT] Once everything has been pushed to branch 3.13, you can continue with the release by adding a @quarkusbot continue comment.

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

This can happen if, for instance, an important regression is detected just after the `3.13.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.13.1` release as usual. The instructions will be automatically adapted.

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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

gsmet commented 1 month ago

@quarkusbot continue

github-actions[bot] commented 1 month ago

: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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

github-actions[bot] commented 1 month ago

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

github-actions[bot] commented 1 month ago

:white_check_mark: 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.13.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?

- [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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

quarkusbot commented 1 month ago

@quarkusbot continue

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

github-actions[bot] commented 1 month ago

: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 - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update quickstarts - Additional sync to version branch - [ ] Update documentation - [ ] Announce release

github-actions[bot] commented 1 month ago

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

github-actions[bot] commented 1 month ago

:white_check_mark: 3.13.0 was successfully released.

:raised_hands: 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.13.0

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/39032[#39032] - Otel metrics support
* https://github.com/quarkusio/quarkus/issues/39033[#39033] - Add support for OpenTelemetry metrics.
* https://github.com/quarkusio/quarkus/pull/41258[#41258] - ArC: support interception of producers and synthetic beans
* https://github.com/quarkusio/quarkus/pull/41368[#41368] - Add new `WithTestResource` annotation and deprecate `QuarkusTestResource`
* https://github.com/quarkusio/quarkus/pull/41418[#41418] - Add TLS CLI commands
* https://github.com/quarkusio/quarkus/pull/41457[#41457] - Provide a configuration option for disabling live-reload
* https://github.com/quarkusio/quarkus/pull/41501[#41501] - Cert-Manager support and TLS periodic reload
* https://github.com/quarkusio/quarkus/pull/41521[#41521] - Bump OTel 1.39. and instrumentation to 2.5.0
* https://github.com/quarkusio/quarkus/pull/41760[#41760] - WebSockets Next: add support for Kotlin suspend functions
* https://github.com/quarkusio/quarkus/pull/41786[#41786] - Otel metrics part2 - Metrics documentation 
* https://github.com/quarkusio/quarkus/pull/41804[#41804] - Introduce the ability to automatically standup an HTTP proxy for the REST Client

Other breaking changes (FYI, in Asciidoc)

* https://github.com/quarkusio/quarkus/pull/41203[#41203] - Improve Config CLI
* https://github.com/quarkusio/quarkus/pull/41244[#41244] - Set extension properties directly
* https://github.com/quarkusio/quarkus/pull/41405[#41405] - Remove OpenTelemetry old Config relocations and fallbacks
* https://github.com/quarkusio/quarkus/pull/41614[#41614] - Redis Client: fix JSON.MGET parameters ordering
* https://github.com/quarkusio/quarkus/pull/41710[#41710] - Introduce support for canceling async types in Quarkus Rest

It might also be a good idea to have a look at the migration guide for this version.

Announcement email template

Subject:

[RELEASE] Quarkus 3.13.0

Body:

Hello,

Quarkus 3.13.0 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-13-0-released/.

* Major changes:

  * [#39032] Otel metrics support
  * [#39033] Add support for OpenTelemetry metrics.
  * [#41258] ArC: support interception of producers and synthetic beans
  * [#41368] Add new `WithTestResource` annotation and deprecate `QuarkusTestResource`
  * [#41418] Add TLS CLI commands
  * [#41457] Provide a configuration option for disabling live-reload
  * [#41501] Cert-Manager support and TLS periodic reload
  * [#41521] Bump OTel 1.39. and instrumentation to 2.5.0
  * [#41760] WebSockets Next: add support for Kotlin suspend functions
  * [#41786] Otel metrics part2 - Metrics documentation 
  * [#41804] Introduce the ability to automatically standup an HTTP proxy for the REST Client

* BOM dependency:

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

* Changelogs are available from https://github.com/quarkusio/quarkus/releases/tag/3.13.0.CR1 and https://github.com/quarkusio/quarkus/releases/tag/3.13.0
* Download is available from https://github.com/quarkusio/quarkus/releases/tag/3.13.0
* 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.12.0'..'3.13.0' | cut -d$'\t' -f 2 | grep -v dependabot | grep -v quarkusbot | sort -d -f -i | paste -sd ',' - | sed 's/,/, /g'

quarkus-release / release

3.13.0 #80

Branch

Origin branch

Qualifier

Major version

Trigger performance testing

Announce release

Newsworthy changes (in Asciidoc)

Other breaking changes (FYI, in Asciidoc)

Announcement email template