Creating a Release
These are the steps in order to create a new release for cri-dockerd. These steps will need to be done by a project maintainer.
- Setup the repo for a new release
- Change the version found in
VERSION,cmd/version/version.go, andpackaging/common.mkto the new version - Create a PR with these changes and merge them to master
- Build the release artifacts using
make release - Verify the artifacts in the
build/releasedirectory and make sure they look correct
- Change the version found in
- A maintainer creates a new draft release in the project’s releases section
- The name should follow semantic convention prepended with a ‘v’
- A tag with the same name should be created on the latest commit to master from the previous step
- Release notes should be generated using the previous tag and the new tag as the range
- Check the box to Set as a pre-release
- Upload the release artifacts from the previous step
- Save as a draft
- The release can now go through a review process to look for any issues
- Change the draft to a published release
- Celebrate :cheers: