From b94853d1f0f3f48096eeb20a5fddf193bd140ba5 Mon Sep 17 00:00:00 2001
From: Matt Brictson <matt@mattbrictson.com>
Date: Tue, 11 Feb 2020 09:15:14 -0800
Subject: [PATCH] Release 3.12.0

---
 README.md                 | 2 +-
 RELEASING.md              | 2 +-
 lib/capistrano/version.rb | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 690fccdc..7369654d 100644
--- a/README.md
+++ b/README.md
@@ -107,7 +107,7 @@ Add Capistrano to your project's Gemfile using `require: false`:
 
 ``` ruby
 group :development do
-  gem "capistrano", "~> 3.11", require: false
+  gem "capistrano", "~> 3.12", require: false
 end
 ```
 
diff --git a/RELEASING.md b/RELEASING.md
index ef7ad15d..a74c119a 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -12,6 +12,6 @@
 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`.
 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.
 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
diff --git a/lib/capistrano/version.rb b/lib/capistrano/version.rb
index 60465780..68eec3cd 100644
--- a/lib/capistrano/version.rb
+++ b/lib/capistrano/version.rb
@@ -1,3 +1,3 @@
 module Capistrano
-  VERSION = "3.11.2".freeze
+  VERSION = "3.12.0".freeze
 end