3.10.0 - Githubissues

gsmet commented 2 months ago

Branch

3.10

Qualifier

No response

Major version

[ ] This release is a major version.

github-actions[bot] commented 2 months ago

:gear: Proceeding to step Prerequisites

You can follow the progress of the workflow here.

github-actions[bot] commented 2 months ago

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

Quarkus 3.10.0
On branch 3.10
With Java 17

:bulb: 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 2 months ago

@quarkusbot yes

github-actions[bot] commented 2 months 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 2 months ago

: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] commented 2 months ago

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

: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 1 hour (starting from the time of this comment) * Check that https://repo1.maven.org/maven2/io/quarkus/quarkus-bom/3.10.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 2 months ago

@quarkusbot continue

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

github-actions[bot] commented 2 months 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 2 months ago

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

github-actions[bot] commented 2 months 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.

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.10.0
./update-quarkus-version.sh 3.10.0

Check the diff with git diff

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

Body:

Hi,

The Quarkus 3.10.0 core artifacts are available on Maven Central.

The pull request updating the Platform to Quarkus 3.10.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 :warning: 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.10
git push upstream 3.10

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

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

This can happen if, for instance, an important regression is detected just after the `3.10.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.10.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 2 months ago

@quarkusbot continue

github-actions[bot] commented 2 months 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 2 months ago

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

github-actions[bot] commented 2 months ago

: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.10.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 2 months ago

@quarkusbot continue

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

github-actions[bot] commented 2 months 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 2 months ago

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

github-actions[bot] commented 2 months ago

:white_check_mark: 3.10.0 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.10.0

to trigger the performance evaluation testing for this 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/

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

Newsworthy changes (in Asciidoc)

* https://github.com/quarkusio/quarkus/pull/36504[#36504] - Allow authentication mechanism selection for a REST endpoint with annotation
* https://github.com/quarkusio/quarkus/pull/37816[#37816] - Optional support for the OIDC session cookie dir encryption
* https://github.com/quarkusio/quarkus/pull/39295[#39295] - Move package config to an interface
* https://github.com/quarkusio/quarkus/pull/39415[#39415] - Extension for the Hibernate Search Standalone Pojo Mapper with Elasticsearch
* https://github.com/quarkusio/quarkus/pull/39509[#39509] - Update Flyway to 10.10.0
* https://github.com/quarkusio/quarkus/pull/39793[#39793] - Support for verifying OIDC JWT claims with custom Jose4j `Validator`
* https://github.com/quarkusio/quarkus/pull/39812[#39812] - Support resolving of static OIDC tenants based on token issuers
* https://github.com/quarkusio/quarkus/pull/40056[#40056] - Add OIDC TokenCertificateValidator

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.10.0

Body:

Hello,

Quarkus 3.10.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-10-0-released/.

* Major changes:

  * [#36504] Allow authentication mechanism selection for a REST endpoint with annotation
  * [#37816] Optional support for the OIDC session cookie dir encryption
  * [#39295] Move package config to an interface
  * [#39415] Extension for the Hibernate Search Standalone Pojo Mapper with Elasticsearch
  * [#39509] Update Flyway to 10.10.0
  * [#39793] Support for verifying OIDC JWT claims with custom Jose4j `Validator`
  * [#39812] Support resolving of static OIDC tenants based on token issuers
  * [#40056] Add OIDC TokenCertificateValidator

* BOM dependency:

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

* Changelogs are available from https://github.com/quarkusio/quarkus/releases/tag/3.10.0.CR1 and https://github.com/quarkusio/quarkus/releases/tag/3.10.0
* Download is available from https://github.com/quarkusio/quarkus/releases/tag/3.10.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.9.0'..'3.10.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.10.0 #62

Branch

Qualifier

Major version

Newsworthy changes (in Asciidoc)

Announcement email template