Contents

# Releasing

1. Update the version number in these places:

    - `lib/bitters/version.rb`
    - `core/_base.scss`
    - `package.json`

1. Update `CHANGELOG.md`. We follow the guidelines from
   [Keep a Changelog][keep-a-changelog].

1. 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.

1. Run `bundle exec rake release`, which tags the release, pushes the tag to
   GitHub, and pushes the gem to RubyGems.org.

1. Draft a [new GitHub release][github-release].

1. Tweet about the release from the [@bourbonsass] Twitter account, e.g.

    > We’ve released Bitters {release_title}: {release_link}

1. If needed, update the [contributing page].

[keep-a-changelog]: https://keepachangelog.com/en/1.0.0/
[github-release]: https://github.com/thoughtbot/bitters/releases/new
[@bourbonsass]: https://twitter.com/bourbonsass
[contributing page]: https://github.com/thoughtbot/bitters/blob/master/contrib/index.html

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
bitters-2.0.4	RELEASING.md
bitters-2.0.3	RELEASING.md
bitters-2.0.2	RELEASING.md