-
Merge any relevant pull requests into the
main
branch. -
Pull down the latest version of the
main
branch.git pull origin main
-
Checkout a new branch for the release from
main
, e.g.git checkout -b release-version-1.0.0
-
Update
CHANGELOG.md
with the current date, new gem version, and release notes. -
Update the
Installation
section ofREADME.md
to list the new gem version. -
Update the value of
s.version
inpundit-matchers.gemspec
to use the new gem version. -
Run the
bundle
command to include the new gem version inGemfile.lock
. -
Commit the release changes to the branch, e.g:
git commit -am "Release version 1.0.0"
-
Push the changes up to GitHub:
git push origin release-version-1.0.0
-
Verify that all CI jobs pass.
-
Release the gem:
rake release
This command automates the gem release process by building the gem file, publishing it to RubyGems.org, creating a release tag with a version number prefixed by
v
, and pushing the tag to GitHub, simplifying the steps required to distribute and mark a specific version of the gem. -
Create a GitHub release, using the tag for the release (e.g.
v1.0.0
), at the following URL:https://github.com/pundit-community/pundit-matchers/releases/new
-
Create a pull request and, once approved, merge the release branch into
main
.