summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2017-05-23 16:16:03 -0500
committerTim Smith <tsmith@chef.io>2017-05-23 16:16:03 -0500
commit2884bc06cfed4de0a8a03a5d0aec7e084f33b8de (patch)
tree8f482648be59b81cd79e5573dc8b4a7d27e831f4
parent5cab1ac5b2b45b426548425ed08d0807ea03e42a (diff)
downloadchef-2884bc06cfed4de0a8a03a5d0aec7e084f33b8de.tar.gz
Update release notes for 13.1
Signed-off-by: Tim Smith <tsmith@chef.io>
-rw-r--r--RELEASE_NOTES.md10
1 files changed, 9 insertions, 1 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index e01bfc9097..a663b6457c 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -1,6 +1,6 @@
_This file holds "in progress" release notes for the current release under development and is intended for consumption by the Chef Documentation team. Please see <https://docs.chef.io/release_notes.html> for the official Chef release notes._
-# Chef Client Release Notes 13.0:
+# Chef Client Release Notes 13.0-13.1:
## Rubygems provider sources behavior changed.
@@ -384,3 +384,11 @@ The implementation switched to `shell_out_with_systems_locale` to match `execute
Chef Client will only exit with exit codes defined in RFC 062. This allows other tooling to respond to how a Chef run completes. Attempting to exit Chef Client with an unsupported exit code (either via `Chef::Application.fatal!` or `Chef::Application.exit!`) will result in an exit code of 1 (GENERIC_FAILURE) and a warning in the event log.
When Chef Client is running as a forked process on unix systems, the standardized exit codes are used by the child process. To actually have Chef Client return the standard exit code, `client_fork false` will need to be set in Chef Client's configuration file.
+
+## New Deprecations
+
+### Removal of support for Ohai version 6 plugins (OHAI-10)
+
+<https://docs.chef.io/deprecations_ohai_filesystem.html>
+
+In Chef/Ohai 14 (April 2018) we will remove support for loading Ohai v6 plugins, which we deprecated in Ohai 7/Chef 11.12.