Contents

# Releasing

1. Update the version number in these places:
  - `lib/neat/version.rb`
  - `core/_neat.scss`
  - `package.json`

1. Update `CHANGELOG.md`

1. Commit changes. Use the convention “Neat 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. Run `npm publish`, which pushes the new version to npm’s registry (if
   releasing a pre-release, run `npm publish --tag beta`).

1. Draft a [new GitHub release].

1. Re-generate and publish the [documentation website].

1. Announce the new release, making sure to say “thank you” to the contributors
   who helped shape this version!

[new GitHub release]: https://github.com/thoughtbot/neat/releases/new
[documentation website]: https://github.com/thoughtbot/neat.bourbon.io

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
neat-4.0.0	RELEASING.md