Closed gsmet closed 5 months ago
:gear: Proceeding to step Prerequisites
You can follow the progress of the workflow here.
We are going to release the following release:
3.6.8
3.6
11
maintenance
release.Please approve with a @quarkusbot yes
comment if you want to continue with the release.
If not, simply close this issue.
@quarkusbot yes
:gear: Proceeding to step Approve the core release
You can follow the progress of the workflow here.
:white_check_mark: Core release is approved, proceeding...
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.
@quarkusbot continue
We have detected that the core artifacts have been synced to Maven Central.
:gear: Proceeding to step Sync core release to Maven Central
You can follow the progress of the workflow here.
:white_check_mark: Core artifacts have been synced to Maven Central, continuing...
Now is time to update Quarkus in the Quarkus Platform. This is a manual process.
upstream
is the upstream repository, origin
is your fork):cd <your quarkus-platform clone>
git checkout 3.6
git pull upstream 3.6
git checkout -b quarkus-3.6.8
./update-quarkus-version.sh 3.6.8
git diff
git add .
git commit -m 'Upgrade to Quarkus 3.6.8'
git push origin quarkus-3.6.8
3.6
(or generic link if targeted link doesn't work)Once everything has been merged to branch 3.6
, you can continue with the release by adding a @quarkusbot continue
comment.
@quarkusbot continue
:gear: Proceeding to step Prepare the Quarkus Platform
You can follow the progress of the workflow here.
:white_check_mark: The Platform branch 3.6
is ready to be released, continuing...
: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.
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.
@quarkusbot continue
:white_check_mark: We have detected that the Platform artifacts have been synced to Maven Central.
:gear: Proceeding to step Sync Platform release to Maven Central
You can follow the progress of the workflow here.
:white_check_mark: Platform artifacts have been synced to Maven Central, continuing...
:rotating_light: An error occurred while executing step Update quickstarts
.
For minor versions, we shouldn't have code updates in the Quickstarts.
So, if you got the build failing, either something got wrongly merged in the main
branch of https://github.com/quarkusio/quarkus-quickstarts/ or something in Quarkus broke the quickstarts.
You can find more information about the failure here.
This is not a fatal error, you can retry by adding a @quarkusbot retry
comment.
@quarkusbot retry
:gear: Proceeding to step Update quickstarts
You can follow the progress of the workflow here.
:white_check_mark: 3.6.8 was successfully released.
Connected to the Red Hat VPN, in a clone of https://github.com/quarkusio/quarkus-release, run:
./trigger-performance-testing.sh 3.6.8
to trigger the performance evaluation testing for this release.
Then it is time to write the announcement:
_data/versions.yaml
Branch
3.6
Qualifier
No response
Major version