CHANGELOG.md in capistrano-3.1.0 vs CHANGELOG.md in capistrano-3.2.0

@@ -1,11 +1,30 @@
 # Capistrano 3.x Changelog
 
 Reverse Chronological Order:
 
+## master
+
+https://github.com/capistrano/capistrano/compare/v3.2.0...HEAD
+
+## `3.2.0``
+
+The changelog entries here are incomplete, because many authors choose not to
+be credited for their work, check the tag comparison link for Github.
+
+https://github.com/capistrano/capistrano/compare/v3.1.0...v3.2.0
+
+* Minor changes:
+  * Added `keys` method to Server properties to allow introspection of automatically added
+    properties.
+  * Compatibility with Rake 10.2.0 - `ensure_task` is now added to `@top_level_tasks` as a string. (@dmarkow)
+  * Amended the git check command, "ls-remote", to use "-h", limiting the list to refs/heads
+
 ## `3.1.0`
 
+https://github.com/capistrano/capistrano/compare/v3.0.1...v3.1.0
+
 Breaking changes:
 
   * `deploy:restart` task **is no longer run by default**.
     From this version, developers who restart the app on each deploy need to declare it in their deploy flow (eg `after 'deploy:publishing', 'deploy:restart'`).
 
@@ -18,11 +37,11 @@
     will only run on servers where the `no_release` property is not falsy. (@leehambley)
   * Fixed bug when `deploy:cleanup` was executed twice by default (@kirs)
   * Config location can now be changed with `deploy_config_path` and `stage_config_path` options (@seenmyfate)
   * `no_release` option is now available (@seenmyfate)
   * Raise an error if developer tries to define `:all` role, which is reserved (@kirs)
-  * `deploy:fallback` hook was added to add some custom behaviour on failed deploy (@seenmyfate)
+  * `deploy:failed` hook was added to add some custom behaviour on failed deploy (@seenmyfate)
   * Correctly infer namespace in task enhancements (@seenmyfate)
   * Add SHA to revision log (@blackxored)
   * Allow configuration of multiple servers with same hostname but different ports (@rsslldnphy)
   * Add command line option to control role filtering (@andytinycat)
   * Make use of recent changes in Rake to over-ride the application name (@shime)
@@ -35,16 +54,20 @@
 
 Big thanks to @Kriechi for his help.
 
 ## `3.0.1`
 
+https://github.com/capistrano/capistrano/compare/v3.0.0...v3.0.1
+
   * `capify` not listed as executable (@leehambley)
   * Confirm license as MIT (@leehambley)
   * Move the git ssh helper to application path (@mpapis)
 
 ## `3.0.0`
 
+https://github.com/capistrano/capistrano/compare/2.15.5...v3.0.0
+
 If you are coming here to wonder why your Capfile doesn't work anymore, please
 vendor lock your Capistrano at 2.x, whichever version was working for you
 until today.
 
 Capistrano 3 is a ground-up rewrite with modularity, stability, speed and
@@ -77,10 +100,10 @@
 extension the trusted contributors and IRC regulars) were able to test for.
 
 There's a more extensive post about my failure to be able to keep up with the
 demands of maintaining v2 whilst trying to build something which is appropriate
 for the current landscape. If you are affected by the unsupported 2 branch,
-please contact me (Lee Hambley) to dicsuss how my company can help support you.
+please contact me (Lee Hambley) to discuss how my company can help support you.
 Otherwise, please try v3, we're sure you'll like it, and the code is designed
 to be so simple that anyone can work on it.
 
 ## `3.0.0.pre14`