I just pushed Chef 12.0.0.alpha.0 to rubygems. Since lots of you follow our activity on github and rubygems (and will notice this release), I’d like to give you an explanation of what’s in this release and our motivation for shipping it now.
First of all, very few of the changes we’ve agreed upon in the RFC process (https://github.com/opscode/chef-rfc/pull/22) have been implemented. If you’re interested in what has changed since we started merging code for 12.0, see the release notes (in progress) here: https://github.com/opscode/chef/blob/bfe0ac206c5723637772d8b9b3a48a4d94f5c21f/RELEASE_NOTES.md
Since there’s still so much left to do, we normally wouldn’t have made an official release of any sort at this point. However, we’ve recently added some library code to the chef-dk application which relies on changes that were in master of chef. Due to some quirks of our build tooling and bundler, ChefDK (the package) doesn’t build correctly when using bundler to fetch dependencies from git. So in order to keep our Ci pipeline happy, we’ve released the 12.0.0.alpha.0 gem to work around these limitations. Note that this will only affect the version of chef that chef-dk (the app) uses as a library, and this change will only show up in nightly builds for now. The
chef-client, and other binaries that come with ChefDK will continue to be built from the stable branch.
Let me know if you have any questions,