CHANGELOG.mkd in r10k-2.4.5 vs CHANGELOG.mkd in r10k-2.5.0
- old
+ new
@@ -1,42 +1,24 @@
CHANGELOG
=========
-2.4.5
+2.5.0
-----
-2016/12/01
+2016/11/15
-(RK-78) Use :prune option for #fetch in Rugged::BareRepository
-
-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.
-
-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.
-
-2.4.4
------
-2016/11/16
-
### Bug Fixes
-(#669) Backport from 2.5.0 - Updated the behavior of the rugged based git
-provider to handle unexpected behavior around checkout and resets regarding
-file permissions, specifically, when resetting to an already checked out SHA
-the executable bit on files would not update.
+(#669) Updated the behavior of the rugged based git provider to handle
+unexpected behavior around checkout and resets regarding file permissions,
+specifically, when resetting to an already checked out SHA the executable bit
+on files would not update.
### Changes
-(#664) Backport from 2.5.0 - Added to the proxy error message for changes made
-to libcurl which gave new, surprising errors about unsupported proxy schemes.
+(#664) Added to the proxy error message for changes made to libcurl which gave
+new, surprising errors about unsupported proxy schemes.
2.4.3
-----
2016/08/23
@@ -94,11 +76,11 @@
(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
+option that can be used to enable new behavior or de-activate certain existing
behaviors. See the relevant [configuration 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
@@ -141,11 +123,11 @@
(RK-236/RK-237) Added HTTP proxy support for Git operations.
Previously, r10k only supported the use of HTTP proxies for connecting to the Puppet
Forge. With these changes, r10k can now be configured to use an HTTP proxy for both
Forge and Git operations. Configuration can be specified globally, for Forge or Git
-only, or on a per-Git repository basis. See [configuration documentation](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd)
+only, or on a per-Git repository basis. See [configuration documentation](https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd)
for more details.
### Bug Fixes
(RK-238) When r10k encounters and ignores invalid file types in a module archive, it
@@ -162,12 +144,12 @@
2016/04/18
(RK-241) "deploy display" action does not properly format wrapped exceptions
The "deploy display" action was not capturing and logging exceptions in the same way as
-other related actions. This meant that in many cases, when an error occurred, the
+other related actions. This meant that in many cases, when an error occurred, the
underlying cause was not being shown. Specifically, the "deploy display" action was
-not benefitting from the improved error messaging for unreadable SSH keys which was
+not benefitting from the improved error messaging for unreadable SSH keys which was
added in r10k 2.2.0 as part of RK-220.
2.2.1
-----