RELEASE.md

Gem Release Process

Don't use the bundle exec rake release task. It is more convenient, but it skips the process of signing the version release task.

Run Tests

$ bundle exec rake test wwtd

Git Push

$ git push

Check for regressions in automated tests.

• https://travis-ci.org/grempe/rack-json_web_token_auth

Bump Version Number and edit CHANGELOG.md

$ vi lib/rack/json_web_token_auth/version.rb
$ git add lib/rack/json_web_token_auth/version.rb
$ vi CHANGELOG.md
$ git add CHANGELOG.md

Local Build and Install w/ Signed Gem

The build step should ask for PEM passphrase to sign gem. If it does not ask it means that the signing cert is not present.

Build:

$ rake build
Enter PEM pass phrase:
rack-json_web_token_auth 0.1.0 built to pkg/rack-json_web_token_auth-0.1.0.gem

Install locally w/ Cert:

$ gem uninstall rack-json_web_token_auth
$ rbenv rehash
$ gem install pkg/rack-json_web_token_auth-0.1.0.gem -P MediumSecurity
Successfully installed rack-json_web_token_auth-0.1.0
1 gem installed

Git Commit Version and CHANGELOG Changes, Tag and push to Github

$ git commit -m 'Bump version v0.1.0'
$ git tag -s v0.1.0 -m "v0.1.0" SHA1_OF_COMMIT

Verify last commit and last tag are GPG signed:

$ git tag -v v0.1.0
...
gpg: Good signature from "Glenn Rempe (Code Signing Key) <[email protected]>" [ultimate]
...

$ git log --show-signature
...
gpg: Good signature from "Glenn Rempe (Code Signing Key) <[email protected]>" [ultimate]
...

Push code and tags to GitHub:

$ git push
$ git push --tags

Push gem to Rubygems.org

$ gem push pkg/rack-json_web_token_auth-0.1.0.gem

Verify Gem Push at https://rubygems.org/gems/rack-json_web_token_auth

Create a GitHub Release

Specify the tag we just pushed to attach release to. Copy notes from CHANGELOG.md

https://github.com/grempe/rack-json_web_token_auth/releases