RELEASING.md

Releasing

1. Update the version number in these places:

   • lib/neat/version.rb
   • core/_neat.scss
   • package.json

2. Update CHANGELOG.md

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

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

5. Run npm publish, which pushes the new version to npm’s registry (if releasing a pre-release, run npm publish --tag beta).

6. Draft a new GitHub release.

7. Re-generate and publish the documentation website.

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