Instead of tagging a new release on every merge to master, this takes advantage of GitHub Releases to release a new version.
This switches over to the git-version-bump gem (https://github.com/rbclark/git-version-bump) which uses the git tag at the time of building to determine the version. This means no more updating the version.rb on every release, meaning 33% less commits to master.
Changelog is still built on every commit and will show the currently merged but unreleased changes under "Unreleased". AFTER a tag is created, a new Changelog will be automatically pushed to master.
The steps to do so in the future are included in the README and are included here for reference:
Publishing a Release
If you are a maintainer, it is very easy to cut a release of this gem:
Click on "Releases" and there should be a draft pending.
Make sure the Tag version and Release title match!
Add any additional notes can be added in the Description box.
Click "Publish release".
Release notes will be posted and a new gem will be pushed to Rubygems & Github Packages with the version you specified on step 2.
Instead of tagging a new release on every merge to master, this takes advantage of GitHub Releases to release a new version.
This switches over to the git-version-bump gem (https://github.com/rbclark/git-version-bump) which uses the git tag at the time of building to determine the version. This means no more updating the version.rb on every release, meaning 33% less commits to master.
Changelog is still built on every commit and will show the currently merged but unreleased changes under "Unreleased". AFTER a tag is created, a new Changelog will be automatically pushed to master.
The steps to do so in the future are included in the README and are included here for reference:
Publishing a Release
If you are a maintainer, it is very easy to cut a release of this gem: