Skip to content

Latest commit

 

History

History
72 lines (52 loc) · 1.71 KB

RELEASE.md

File metadata and controls

72 lines (52 loc) · 1.71 KB
Raw

Release

Before You Begin

Ensure your local workstation is configured to be able to Sign commits.

Local Release Preparation

Checkout latest code

$ git checkout main
$ git pull origin main

Bump version

Update version in lib/toxiproxy/version.rb. Check if there is required changes in README.md. Add line after ## [Unreleased] in [CHANGELOG.md][./CHANGELOG.md] with new version and update links to commits compare in the bottom of the document.

Run Tests

Make sure all tests passed and gem could be build

$ toxiproxy-server
$ rake test
$ rake build

Create Release Commit and Tag

Commit changes and create a tag. Make sure commit and tag are signed. Extract related content from [CHANGELOG.md][./CHANGELOG.md] for a tag message.

$ export RELEASE_VERSION=2.x.y
$ git commit -a -S -m "Release $RELEASE_VERSION"
$ git tag -s "v$RELEASE_VERSION"

Release Tag

On your local machine again, push your commit and tag

$ git push origin main --follow-tags

Verify rubygems release

  • Shipit should kick off a build and release after new version detected.
  • Check rubygems

Github release

  • Create a new gem 
    $ bundle exec rake build
  • Create github release. Choose either hub or gh.
    • Github CLi gh_release_create : 
      $ gh release create v<version> pkg/toxiproxy-<version>.gem
    • Hub: 
      $ hub release create -a pkg/toxiproxy-<version>.gem v<version>