The following checklist covers all the steps for running release.
First, a pre-release is published which is used to ensure all systems operate
correctly in development environments. Once the pre-release is confirmed to be
working, the final release is published.
or gh pr create --template=release_template.md a closes issue #x in the body will automatically close this issue on merge.
Generating Release notes
To get a starting point for generating release notes the view-changelog script can be used.
git cliff is used to generate a changelog update. The view-changelog script can be used to view
the new entries or modifty the CHANGELOG.md file.
To view the changelog updates:
actions/view-changelog.sh
or to prepend the updates (some post editing is still usually required):
Release Checklist
The following checklist covers all the steps for running release.
First, a pre-release is published which is used to ensure all systems operate correctly in development environments. Once the pre-release is confirmed to be working, the final release is published.
For more detail, refer to
RELEASE.md
Pre-Release
Release
workflow in Github Actions, make sure thepre-release
check is set. (Retry at least once if failure)Stable Release
If all systems are operational and no bugs are found in the pre-release, the final release can be published.
VERSION
andCHANGELOG.md
files (do not place a \n in the VERSION file, it breaks the CI)Release
workflow in Github Actions without thepre-release
check.release_template.md
template=release_template.md
to the PR URL while creating in order to use templategh pr create --template=release_template.md
a closes issue #x in the body will automatically close this issue on merge.Generating Release notes
To get a starting point for generating release notes the view-changelog script can be used. git cliff is used to generate a changelog update. The view-changelog script can be used to view the new entries or modifty the CHANGELOG.md file.
To view the changelog updates:
actions/view-changelog.sh
or to prepend the updates (some post editing is still usually required):
actions/view-changelog.sh modify