v0.8.0

FEATURES:

• Support using chef-runner on Windows. New releases will include
  cross-compiled Windows binaries. Requires ssh.exe and rsync.exe to be
  installed. ssh.exe is included in MinGW (Git Bash). rsync.exe must be
  configured to use destination-default permissions when provisioning Unix-like
  systems: chef-runner --rsync --no-p --rsync --no-g --rsync --chmod=ugo=rwX.
• Allow to specify one or more custom OpenSSH options on the command line, e.g.
  chef-runner --ssh LogLevel=debug --ssh "ProxyCommand ...". See
  ssh_config(5) for a list of available options and their format. (Thanks to
  @berniedurfee who requested this feature.)
• Allow to specify one or more custom Rsync options on the command line, e.g.
  chef-runner --rsync --progress. See rsync(1) for a list of available
  options.
• Add --color=false option to disable colorized output.

IMPROVEMENTS:

• Support standard Chef syntax for composing the run list: entries may be
  separated by comma, and an entry named foo will now expand to foo::default
  (see BREAKING CHANGES for more information). As a result, something like
  chef-runner recipe[cats],dogs::bar now does what Chef users would expect.
• Install Chef using a smart shell wrapper around Omnibus Installer instead of
  running complicated shell commands over SSH. Move installer logic from Chef
  Solo provisioner to new omnibus package.
• The option --version now also outputs the Go version that was used to
  compile chef-runner.

BREAKING CHANGES:

• Adapt run list syntax to Chef's standard: a run list entry named foo will
  now expand to foo::default. Before, foo was treated as a local recipe and
  expanded to <cookbook>::foo. Local recipes now need to be passed as ::foo
  instead. This change also simplifies run list composition when multiple
  cookbooks are involved, e.g. chef-runner apt postgresql::client nginx.
• No longer run Rsync in verbose mode by default. To get back the old output,
  you need to use --rsync --verbose now.