Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds composite actions for an automated release PR and associated tag + GitHub release when the release PR is merged. Builds on prior work in collaboration with @tchataigner (1, 2)
release-pr.yml
Major/minor release
workflow_dispatch
, withmajor
orminor
as therelease-type
inputrelease/<tag-prefix>-v<version>
branch, e.g.release/aptos-v1.0
. Note thatrelease/
branches omit the SemVer patch version, as they are meant to persist for production and will iteratively incorporate any patches/hotfixes.release/aptos-v1.1
release-pr
that increments the version number inCargo.toml
, e.g.1.0.0
to1.1.0
release-pr
to the newrelease/
branch. This allows for CI, PR review, and any additional commits to be added for the release. These commits should generally be cherry-picked from existing commits to the default branch.tag-release
workflow. Therelease-pr
branch can be safely deleted, but therelease/
branch should be kept as the release source.Patch release
workflow_dispatch
, withpatch
as therelease-type
inputrelease/<tag-prefix>-v<version>
branch, e.g.release/aptos-v1.0
patch/<tag-prefix>-v<version>.<patch-version>
, e.g.patch/aptos-v1.0.1
, which increments the version number inCargo.toml
accordinglypatch/
branch to the newrelease/
branch. This allows for CI, PR review, and any additional commits to be added for the release.tag-release
workflow. Thepatch/
branch can be safely deleted, but therelease/
branch should be kept as the release source.tag-release.yml
release-pr
caller when the release PR is merged, as it relies on the head and base branch names for tagging.Downstream examples
Successful runs
TODOs
Cargo.toml
version if this is the latestmajor.minor
release