-
Update the version number in these places:
lib/bitters/version.rb
core/_base.scss
package.json
-
Update
CHANGELOG.md
. We follow the guidelines from Keep a CHANGELOG. -
Commit changes. Use the convention “Bitters vX.X.X” in your commit message. There shouldn’t be code changes, and thus CI doesn’t need to run.
-
Run
bundle exec rake release
, which tags the release, pushes the tag to GitHub, and pushes the gem to RubyGems.org. -
Draft a new GitHub release. Upon publishing, a tweet will automatically be sent on the @bourbonsass Twitter account via Zapier. It will look like this:
We’ve released Bitters {release_title}: {release_link}
-
If needed, update the contributing page and website example page.