CHANGELOG.mkd in r10k-2.3.1 vs CHANGELOG.mkd in r10k-2.4.0

@@ -1,25 +1,52 @@
 CHANGELOG
 =========
 
-2.3.1
+2.4.0
 -----
 
-2016/11/30
+2016/08/10
 
-(RK-78) Use :prune option for #fetch in Rugged::BareRepository
+### New Features
 
-Versions of the "rugged" gem prior to 0.24.0 lacked the ability to automatically
-"prune" branches from a local repo that no longer existed in the matching remote
-repo after a fetch. To work around this issue, r10k included code that would
-manually remove/recreate branches during a fetch. Since "rugged" 0.24.0 is now
-widely available, r10k has been updated to use the built-in "prune" option
-during a fetch and the workaround code has been removed.
+(RK-222) New "install\_path" option for Git/SVN content.
 
-NOTE: If you use the "rugged" gem with r10k, you will need to manually upgrade
-it to a version >= 0.24.0 to take advantage of the new functionality. If you
-are using a "rugged" version less than 0.24.0, r10k will now issue a warning
-every time it fetches from a remote git repository.
+This feature allows you to specify where inside an environment each item from the
+Puppetfile should be installed to. See the [Puppetfile documentation](https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#per-item-install-path) for details.
+
+(RK-246) New "environment" level purging and configurable purge levels.
+
+You can now configure how r10k purges unmanaged content after a deployment. The
+default behavior should be unchanged but there is a new "purge\_levels" configuration
+option that can be used to enable new behavior or de-activate certain existing 
+behaviors. See the relevant [configration documentation](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#purge_levels) for more details.
+
+(RK-223) Ability to track control repo branch from content declarations.
+
+Puppetfile content sourced from Git can now be configured to attempt to track the branch
+name of the control repo branch being deployed. For example, if r10k is deploying
+the 'production' branch of your control repo, it will try to also deploy the
+'production' branch of a given Puppetfile content repo. See the [documentation](https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#control-repo-branch-tracking)
+for more details.
+
+### Internationalization
+
+All user-facing strings generated by r10k have been externalized to enable future
+iternationalization (i18n) and localization work.
+
+### Changed
+
+(RK-258) Symlinks inside of Forge modules will no longer cause r10k to exit non-zero.
+This situation used to raise an error but will now generate a WARN level log message
+instead.
+
+### Bug Fixes
+
+(#616) Ensure that Forge module version strings are valid semantic versions. (Special
+thanks to Patrick Robinson (patrobinson) for the fix.)
+
+(#622) Fix typos in workflow docs. (Special thanks to Yury Frolov (mrdracon) for the
+fix.)
 
 2.3.0
 -----
 
 2016/05/17