Skip to content

Latest commit

 

History

History
28 lines (24 loc) · 1.71 KB

RELEASE.md

File metadata and controls

28 lines (24 loc) · 1.71 KB
Raw

Heroku CLI Release Process

  • Ensure CI is passing bundle exec rake ci

  • Update version number in /lib/heroku/version.rb to X.Y.Z

  • Run bundle install to update the version of heroku in the Gemfile.lock

  • Update changelog.txt

  • Stage the changes git add .

  • Commit the changes git commit -m "vX.Y.Z"

  • Push the git push origin master

  • Ensure CI still passes bundle exec rake ci

  • Ensure fisticuffs passes by starting a build at http://dx-jenkins.herokai.com/, you can open with bundle exec rake jenkins

  • Move to a checkout of the toolbelt repo and make sure everything is up to date git pull

  • Move to the components/heroku directory, git fetch and git reset --hard HASH where HASH is commit hash of vX.Y.Z

  • Stage git add ., commit git commit -m "bump heroku submodule to vX.Y.Z", and push git push submodule changes

  • Release the gem bundle exec rake release

  • Start toolbelt-build build at http://dx-jenkins.herokai.com/ (this will be opened by rake release automatically)

  • Update current version with Setting.set('current-heroku-client-version', 'X.Y.Z') on core.

  • If there are only bug fixes, you are done, otherwise create a changelog describing features as below

  • Create a [new changelog] => http://devcenter.heroku.com/admin/changelog_items/new, you can open with bundle exec rake changelog

  • Paste the contents of your clipboard (or enter text based on the following):

  • Set the title to Heroku CLI vX.Y.Z released with #{highlights}

  • Set the description to:

      A new version of the Heroku CLI is available with #{details}.

  See the [CLI changelog](https://github.com/heroku/heroku/blob/master/CHANGELOG) for details and update by using `heroku update`.