This document describes the steps to release a new version of DNSimple/CLI.
- You have commit access to the repository
- You have push access to the repository
- You have a GPG key configured for signing tags
- The repository GitHub Actions secrets required for release publishing are configured
-
Determine the new version using Semantic Versioning
VERSION=X.Y.Z
- MAJOR version for incompatible API changes
- MINOR version for backwards-compatible functionality additions
- PATCH version for backwards-compatible bug fixes
-
Run tests and confirm they pass
go test -v ./... -
Update the changelog with the new version
Finalize the
## Unreleasedsection inCHANGELOG.mdassigning the version. -
Commit the new version
git commit -a -m "Release $VERSION" -
Push the changes
git push origin main
-
Wait for CI to complete
-
Create a signed tag
git tag -a v$VERSION -s -m "Release $VERSION" git push origin --tags
- Verify the GitHub release was created in
dnsimple/cli - Verify the Homebrew formula was updated in
dnsimple/homebrew-tap - Announce the release if necessary