The google-cloud-ruby library uses semantic versioning. Replace the <prev_version>
and <version>
placeholders shown in the examples below with the appropriate numbers, e.g. 0.1.0
and 0.2.0
.
After all pull requests for a release have been merged and all Travis CI builds are green, you may create a release as follows:
- Build the google-cloud-ruby gem locally.
$ rake build
- Install the google-cloud-ruby gem locally.
$ rake install
-
Using IRB (not
rake console
!), manually test the gem that you installed in the previous step. -
Open the GitHub compare view in your browser.
open https://github.com/GoogleCloudPlatform/google-cloud-ruby/compare/v<prev_version>...master
-
Review the commits in the GitHub compare view, making notes of significant changes. (For examples of what a significant change is, browse the changes in the CHANGELOG.md.
-
If you haven't already, switch to the master branch, ensure that you have no changes, and pull from origin.
$ git checkout master
$ git status
$ git pull --rebase
-
Edit CHANGELOG.md. Using your notes from the previous step, write bullet-point lists of the major and minor changes. You can also add examples, fixes, thank yous, and anything else helpful or relevant. See gcloud-node v0.18.0 for an example with all the bells and whistles.
-
Edit lib/gcloud/version.rb, changing the value of
VERSION
to your new version number. -
Commit your changes. Copy and paste the significant points from your
CHANGELOG.md
edit as the description in your commit message.
$ git commit -am "Bump for version <version> ... "
- Ensure again that you have every commit from
origin master
.
$ git pull --rebase
- Tag the version.
$ git tag -m 'v<version>' v<version>
- Push your commit.
$ git push
- Push your tag.
$ git push --tags
-
On the google-cloud-ruby releases page, click Draft a new release. Complete the form. Include the bullet-point lists of the major and minor changes from CHANGELOG.md. You can also add examples, fixes, thank yous, and anything else helpful or relevant. See gcloud-node v0.18.0 for an example with all the bells and whistles.
-
Click
Publish release
. -
Check that the Travis CI build has passed for the version commit.
-
Confirm that the gem for the new version is available on RubyGems.org.
-
Confirm that the new version is displayed after "Latest release" on the google-cloud-ruby gh-pages site.
High fives all around!