v3.3.4

• Update nokogiri gem (1.6.8 released).
• Update stove gem to 4.1.

v3.3.3

• Remove extra link bracket in CHANGELOG.
• Update stove to 4.0.0.
• Use Ruby 2.3.1 for Travis and wercker.

v3.3.2

• Add wercker.yml to chefignore.

v3.3.1

• Add berks install as CI step.

v3.3.0

• Add wercker support.
• Add workarounds for CI issues: use nokogiri release candidate and update bundler version.
• Update other dependency versions.
• Update chef and berkshelf with less strict versions.
• Update makenew README section.
• The ./makenew.sh script now removes the Unlicense notice.

v3.2.0

• Guard now watches all files that generate the README.
• Fix some cases of extra spacing in README.
• Remove test/integration/default/serverspec/spec_helper.rb and merge into test file.

v3.1.0

• Add stove.
• Sort Rake tasks.
• Remove makenew badge.
• Minor README changes.

v3.0.0

• Quickly bootstrap your new project with ./makenew.sh.

Updating exiting projects

This version introduces makenew.sh which automatically bootstraps new projects.
Most of the boilerplate which is normally replaced when making a new project has thus been changed.

This will generate a lot of merge conflicts for exiting projects updating to this version, however all of these can be safely ignored.

Recommend update procedure

1. Update normally to chef-cookbook-v2.1.0 by following the instructions in the README (merge in the chef-cookbook-v2.1.0 tag instead of upstream/master).

2. Merge in this version, but only use your file versions. For example,

   $ git fetch upstream
   $ git merge --no-commit chef-cookbook-v3.0.0
   $ git reset .
   $ git checkout --ours .
   $ git clean -fdx
   $ git commit
   

3. Update to the latest release normally.

Alternative update option

Depending on how complicated your merge conflicts are, this manual way may be easier.

1. Checkout this version (or the latest one) into a separate branch, say makenew.
2. Run ./makenew.sh and enter in the values as if you were recreating your work from scratch. Commit the results.
3. Create a new branch from your master and merge the makenew branch (do not create a merge commit yet). Compare the makenew branch to your master branch using git diff and whatever git workflow makes sense. One option is to git reset and git checkout, then update each file one at a time until you are satisfied with the merge.

v2.1.0

• Update Chef to 12.7
• Update and use less strict gem versions.
• Set require_chef_omnibus to true.
• Update some code style for Rubocop.
• Remove rake travis and change default rake task.
• Minor updated to .travis.yml.
• Improve, add to README, and update badges.
• Update .gitignore and chefignore.
• Update Change Log to follow keepachangelog.com.

v2.0.1

• Update dependencies.
• Add more metadata fields.
• Use single quotes in specs and tests.
• Better Guard watchers.
• Better ChefSpec config.
• Improve README.