### `chef_version` and `ohai_version` see: https://docs.chef.io/release/12-6/release_notes.html#new-metadata-rb-settings The metadata.rb DSL is extended to support `chef_version` and `ohai_version` to establish ranges of chef and ohai versions that the cookbook supports. When the running chef or ohai version does not match, then the chef-client run will abort with an exception immediately after cookbooks have been synchronized before any cookbook contents are parsed. The format of the dependencies is based on rubygems (and implemented with rubygems code). Pessimistic version constraints, floor and ceiling constraints, and specifying multiple constraints are all valid. Examples: ``` # matches any 12.x version, but not 11.x or 13.x chef_version "~> 12" ``` ``` # matches any 12.x, 13.x, etc version chef_version ">= 12" ``` ``` # matches any chef 12 version >= 12.5.1 or any chef 13 version chef_version ">= 12.5.1", "< 14.0" ``` ``` # matches chef 11 >= 11.18.4 or chef 12 >= 12.5.1 (i.e. depends on a backported bugfix) chef_version ">= 11.18.12", "< 12.0" chef_version ">= 12.5.1", "< 13.0" ``` As seen in the last example multiple constraints are OR'd. There is currently no support in supermarket for making this metadata visible in /universe to depsolvers, or support in Berksfile/PolicyFile for automatically pruning cookbooks that fail to match. ### `chocolatey_package` and `ksh` resources Assuming both of those make 12.6, placeholder pages: chocolatey_package: https://docs.chef.io/release/12-6/resource_chocolatey_package.html ksh: https://docs.chef.io/release/12-6/resource_ksh.html