CONTRIBUTING.md in rubocop-ruby2_7-1.1.1 vs CONTRIBUTING.md in rubocop-ruby2_7-1.1.2

@@ -9,16 +9,17 @@
 
 ## Release
 
 To release a new version:
 
-1. update the version number in `version.rb`
-2. run `bundle exec rake build:checksum`
-3. move the built gem to project root
-4. run `bin/checksum` to create the missing SHA256 checksum
-5. move the built gem back to `pkg/`
-6. commit the changes
-7. run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org][rubygems].
+1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check.
+2. update the version number in `version.rb`
+3. run `bundle exec rake build:checksum`
+4. move the built gem to project root
+5. run `bin/checksum` to create the missing SHA256 checksum
+6. move the built gem back to `pkg/`
+7. commit the changes
+8. run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org][rubygems].
 
 NOTE: You will need to have a public key in `certs/`, and list your cert in the
 `gemspec`, in order to sign the new release.
 See: [RubyGems Security Guide][rubygems-security-guide]