mirror of
https://github.com/capistrano/capistrano
synced 2023-03-27 23:21:18 -04:00
Release 3.12.0
This commit is contained in:
parent
5e5d918f5e
commit
b94853d1f0
3 changed files with 3 additions and 3 deletions
|
@ -107,7 +107,7 @@ Add Capistrano to your project's Gemfile using `require: false`:
|
||||||
|
|
||||||
``` ruby
|
``` ruby
|
||||||
group :development do
|
group :development do
|
||||||
gem "capistrano", "~> 3.11", require: false
|
gem "capistrano", "~> 3.12", require: false
|
||||||
end
|
end
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
|
@ -12,6 +12,6 @@
|
||||||
3. Determine which would be the correct next version number according to [semver](http://semver.org/).
|
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 `./lib/capistrano/version.rb`.
|
||||||
5. Update the version in the `./README.md` Gemfile example (`gem "capistrano", "~> X.Y"`).
|
5. Update the version in the `./README.md` Gemfile example (`gem "capistrano", "~> X.Y"`).
|
||||||
6. Commit the `version.rb` and `README.md` changes in a single commit, the message should be "Preparing vX.Y.Z"
|
6. Commit the `version.rb` and `README.md` changes in a single commit, the message should be "Release vX.Y.Z"
|
||||||
7. Run `rake release`; this will tag, push to GitHub, and publish to rubygems.org.
|
7. Run `rake release`; this will tag, push to GitHub, and publish to rubygems.org.
|
||||||
8. Update the draft release on the [GitHub releases page](https://github.com/capistrano/capistrano/releases) to point to the new tag and publish the release
|
8. Update the draft release on the [GitHub releases page](https://github.com/capistrano/capistrano/releases) to point to the new tag and publish the release
|
||||||
|
|
|
@ -1,3 +1,3 @@
|
||||||
module Capistrano
|
module Capistrano
|
||||||
VERSION = "3.11.2".freeze
|
VERSION = "3.12.0".freeze
|
||||||
end
|
end
|
||||||
|
|
Loading…
Reference in a new issue