From a1ce7a21120fbcabfb5222deb93ae14f0e5f9c11 Mon Sep 17 00:00:00 2001 From: Matt Brictson Date: Wed, 20 Jul 2016 19:14:01 -0700 Subject: [PATCH] Update version number in README Also add a step to the RELEASING document so that we are less likely to forget this in the future. --- README.md | 2 +- RELEASING.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4e1d1d4a..51f775ac 100644 --- a/README.md +++ b/README.md @@ -103,7 +103,7 @@ Add Capistrano to your project's Gemfile: ``` ruby group :development do - gem "capistrano", "~> 3.4" + gem "capistrano", "~> 3.5" end ``` diff --git a/RELEASING.md b/RELEASING.md index 1dad935a..b110ddc6 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -11,6 +11,7 @@ 2. **Ensure all tests are passing by running `rake spec` and `rake features`.** 3. Determine which would be the correct next version number according to [semver](http://semver.org/). 4. Update the version in `./lib/capistrano/version.rb`. +4. Update the version in the `./README.md` Gemfile example (`gem "capistrano", "~> X.Y"`). 5. Update the `CHANGELOG`. 6. Commit the changelog and version in a single commit, the message should be "Preparing vX.Y.Z" 7. Run `rake release`; this will tag, push to GitHub, and publish to rubygems.org.