Gemfile in chef-dk-3.5.13 vs Gemfile in chef-dk-3.6.57

- old
+ new

@@ -20,13 +20,18 @@ gemspec gem "bundler" group(:omnibus_package, :development, :test) do - gem "rake" + # we pin these gems as they are installed in the ruby source and if we let them + # float we'll end up with 2 copies shipped in DK. When we bump Ruby we need to + # look at these pins and adjust them + gem "rake", "<= 12.3.0" + gem "rdoc", "<= 6.0.1" + gem "minitest", "<= 5.10.3" + gem "pry" - gem "rdoc" gem "yard" gem "guard" gem "cookstyle", ">= 2.0.0" gem "foodcritic", ">= 12.1" gem "ffi-libarchive" @@ -50,10 +55,10 @@ gem "chef-vault", ">= 3.4.1" # Expeditor manages the version of chef released to Rubygems. We only release 'stable' chef # gems to Rubygems now, so letting this float on latest should always give us the latest # stable release. May have to re-pin around major version bumping time, or during patch # fixes. - gem "chef", "= 14.7.17" + gem "chef", "= 14.8.12" gem "cheffish", ">= 14.0.1" gem "chefspec", ">= 7.3.0" gem "fauxhai", ">= 6.7" gem "inspec", ">= 2.3" gem "kitchen-azurerm", ">= 0.14"