* stable:
  (maint) add release date
  (FM-3492) Release 1.1.3

Beaker needs a version of Rake less than 11 due to using
`last_comment' in rake_task.rb:62. Reduce the version of
Rake down to the same dependency that Beaker does as a
development dependency.

Rspec 3+ requires that should be explicitly set as an expect term.
be_true and be_false have also been changed so that they are not
whether something is truthy or falsey, but simply really true/false. To
get the older behavior, the test simply needs to check for be_truthy or
be_falsey. For explicit true/false checks, it is be true and be false.

Remove gem install bundler as part of modulesync updates.

Paired with Glenn Sarti <glenn.sarti at puppetlabs dot com>

(FM-4917) Rake / Beaker / Rspec compatibility

Beaker needs a version of Rake less than 11 due to using
`last_comment' in rake_task.rb:62. Reduce the version of
Rake down to the same dependency that Beaker does as a
development dependency.

Prior to this, the parameters in the defined type, registry::value, were
all on one line and not spaced according to the Puppet Labs style guide.

This commit fixes that by putting each parameter on its own line and
lining everything up.

(maint) Fix the style of the registry::value parameters

(maint) modsync update - stable

* stable:
  (maint) modsync update

Merge stable up to master after modsync changes

(maint) modsync update - master

Update all references from puppetlabs to puppet

…ing-name-change

(MODULES-3356) Branding Name Change

* stable:
  (doc)(MODULES-3356) Branding Name Change

(FM-5236) Use double quotes so $key is interpolated

Module updated with lastest modsync settings

(MODULES-3536) modsync update

* stable:
  (MODULES-3536) modsync update

…on_pure_restriction

(MODULES-3640) Update modulesync 30fc4ab

* stable:
  (MODULES-3640) Update modulesync 30fc4ab

(maint) modulesync 70360747

* origin/stable:
  (maint) modulesync 70360747

* origin/master:
  (FM-5236) Use double quotes so $key is interpolated
  (maint) modsync update - master
  (maint) Fix the style of the registry::value parameters
  (FM-4917) Rake ~> 10.1
  (FM-4917) Rake / Beaker / Rspec compatibility

* pr/113:
  (MODULES-3775) (msync 8d0455c) update travis/appveyer w/Ruby 2.3

* origin/stable:
  (MODULES-3775) (msync 8d0455c) update travis/appveyer w/Ruby 2.3

(MODULES-3704) Update gemfile template to be identical

(MODULES-3632) Use json_pure always

Previously, the registry module only allowed managing keys and
values in HKLM and HKCR. This means the module would not be able to
manage keys in HKU\.DEFAULT, a well-known key store. Allow HKU keys
and values to also be managed with the module.

NOTE: This is not the same as managing a user hive and registry
keys. It is to purely manage the keys and values in HKU.

* pr114:
  (MODULES-3865) Manage keys in HKU (hkey_users)

Workaround frozen strings on ruby 1.9

(FM-5972) Update to next modulesync_configs [dedaf10]

new CI changes require that windows modules have access to blacksmith tasks

The module is throwing a "Munging failed" error when applying a registry
value, more specifically with 64 bit keys/values.  The recommended way to
fix this is to remove the "unless defined?" so that the constant is always
defined on this module.

* pr118:
  (MODULES-3195) Fix WOW64 Constant Definition

(MODULES-4263) add blacksmith rake tasks

(MODULES-4097) Sync travis.yml

(MODULES-4098) Sync the rest of the files

This is no longer a valid bareword.