Release Checklist
- Merge every change meant for the release.
- Check that the latest snapshot was published from the current
maincommit. If not, run Snapshot Release manually. - Run Release from
main. - Approve the
Release Approvalenvironment.
Release explains what the workflow checks and publishes.
When a run fails
Re-run failed jobs uses the original commit and workflow files. Commits pushed to main
after the run started are not included. Use it when the cause is outside this repository, such as
an outage, an expired secret, or charts-docs state.
When the fix needs a new commit, first check whether the version is on Maven Central. The Maven step can fail after the version is already published.
- Not on Maven Central: merge the fix, wait for its snapshot, and run a new Release with
replace_static_assetsenabled. - On Maven Central: the version is final. Finish the remaining steps by hand and ship the fix in the next version.
If only the tag push failed, tag the commit shown in the Approve Release summary:
git tag <version> <source-sha>
git push origin <version>The later jobs stay skipped, so finish the Android build, docs promotion, and GitHub release by hand.