Skip to content

Instantly share code, notes, and snippets.

@krisleech
Last active November 25, 2019 09:48
Show Gist options
  • Select an option

  • Save krisleech/1829e8ae37a7800ed49bbd93cd613f37 to your computer and use it in GitHub Desktop.

Select an option

Save krisleech/1829e8ae37a7800ed49bbd93cd613f37 to your computer and use it in GitHub Desktop.
Releasing Wisper gem

Setup

Ensure commits are always signed: git config commit.gpgsign true

The gem signing private key should exist at ~/.ssh/gem-private_key.pem (see gemspec).

CHANGELOG

Double check the CHANGELOG reflects all commits since last version and all authors are included.

Update the Version

  • Decide on the new version number as per semver, e.g. 1.0.1

  • Add the new version CHANGELOG

  • Update wisper/version.rb (Wisper::VERSION)

  • Commit and Tag

You should be prompted for a GPG password as all commits should be signed.

git commit -m 'v1.0.1'
git push origin master
  • Tag and push
git tag -a 'v1.0.1' -m 'v1.0.1'
git push --tags

Build the gem

Full docs: https://guides.rubygems.org/publishing/

gem build wisper.gemspec --output=pkg/wisper.gem

You should be prompted for the gem signing key password.

Push up to Rubygems

Last chance to abort before the gem becomes public.

You will need a 2FA code when signing in.

gem signin
gem push pkg/wisper.gem

Let um know

Post on Twitter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment