summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLamont Granquist <lamont@scriptkiddie.org>2018-11-19 12:36:42 -0800
committerLamont Granquist <lamont@scriptkiddie.org>2018-11-19 12:36:42 -0800
commit33d65c30cba255c18293fcf2884fc9c2015f27ef (patch)
tree9767d768b2a0771af5a57c441681cb308f08a117
parent79a2ae80fda0e0656d54d0ff295fb911f89e8e57 (diff)
downloadchef-33d65c30cba255c18293fcf2884fc9c2015f27ef.tar.gz
add release notes on possibly breaking behavior change
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
-rw-r--r--RELEASE_NOTES.md23
1 files changed, 23 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index a83367df59..913135f569 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -6,6 +6,29 @@ Chef 15 release notes will be added here as development progresses.
## Breaking Changes
+### Package provider allow_downgrade is now true by default
+
+The behavior of the package provider without any allow_downgrade flag is now to allow downgrades. This will mostly
+affect users of the rpm and zypper package providers.
+
+```
+package "foo" do
+ version "1.2.3"
+end
+```
+
+That code should now be read as asserting that the package `foo` must be version `1.2.3` after that resource is run.
+
+```
+package "foo" do
+ allow_downgrade false
+ version "1.2.3"
+end
+```
+
+That code is now what is necessary to specify that `foo` must be version `1.2.3` or higher. Note that the yum provider
+supports syntax like `package "foo > 1.2.3"` which is preferred to using allow_downgrade and should be used instead.
+
### Node Attributes deep merge nil values
Writing a nil to a precedence level in the node object now acts like any other value and can be used to override values back to nil.