To cut a pre-release:
- If applicable, ensure the README is updated with the latest supported apis (example PR: buildpacks#550).
- Create a release branch in the format
release/0.99.0-rc.1
. New commits to this branch will trigger thebuild
workflow and produce a lifecycle image:buildpacksio/lifecycle:<commit sha>
. - When ready to cut the release, manually trigger the
draft-release
workflow: Actions -> draft-release -> Run workflow -> Use workflow from branch:release/0.99.0-rc.1
. This will create a draft release on GitHub using the artifacts from thebuild
workflow run for the latest commit on the release branch. - Edit the release notes as necessary.
- Perform any manual validation of the artifacts.
- When ready to publish the release, edit the release page and click "Publish release". This will trigger the
post-release
workflow that will re-tag the lifecycle image frombuildpacksio/lifecycle:<commit sha>
tobuildpacksio/lifecycle:0.99.0
but will NOT update thelatest
tag.
To cut a release:
- Ensure the relevant spec APIs have been released.
- Ensure the
lifecycle/0.99.0
milestone on the docs repo is complete, such that every new feature in the lifecycle is fully explained in therelease/lifecycle/0.99
branch on the docs repo, and migration guides (if relevant) are included. - Create a release branch in the format
release/0.99.0
. New commits to this branch will trigger thebuild
workflow and produce a lifecycle image:buildpacksio/lifecycle:<commit sha>
. - If applicable, ensure the README is updated with the latest supported apis (example PR: buildpacks#550) and remove the pre-release note for the latest apis.
- When ready to cut the release, manually trigger the
draft-release
workflow: Actions -> draft-release -> Run workflow -> Use workflow from branch:release/0.99.0
. This will create a draft release on GitHub using the artifacts from thebuild
workflow run for the latest commit on the release branch. - Edit the release notes as necessary.
- Perform any manual validation of the artifacts.
- When ready to publish the release, edit the release page and click "Publish release". This will trigger the
post-release
workflow that will re-tag the lifecycle image frombuildpacksio/lifecycle:<commit sha>
tobuildpacksio/lifecycle:0.99.0
andbuildpacksio/lifecycle:latest
. - Once released
- Update the
main
branch to remove the pre-release note in README.md and/or mergerelease/0.99.0
intomain
. - Ask the learning team to merge the
release/lifecycle/0.99
branch intomain
on the docs repo.