Closed gsmet closed 8 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.5
3.6
11
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.
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.
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.
@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:
cd <your quarkus-platform clone>
git checkout 3.6
git pull upstream 3.6
git checkout -b quarkus-3.6.5
./update-quarkus-version.sh 3.6.5
git diff
git add .
git commit -m 'Upgrade to Quarkus 3.6.5'
git push origin quarkus-3.6.5
3.6
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...
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.
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.
@quarkusbot continue
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...
@quarkusbot retry
:gear: Proceeding to step Update quickstarts
You can follow the progress of the workflow here.
:white_check_mark: 3.6.5 was successfully released.
Time to write the announcement:
_data/versions.yaml
Branch
3.6
Qualifier
No response
Major version