Gemfile in chef-dk-1.4.3 vs Gemfile in chef-dk-1.5.0

- old
+ new

@@ -33,11 +33,11 @@ gem "rdoc" gem "yard" gem "dep_selector" gem "guard" gem "ruby-prof" - gem "cookstyle", ">= 1.3.0" + gem "cookstyle", ">= 1.3.0", "< 2.0" gem "foodcritic", ">= 9.0" end # All software we recognize needs to stay at the latest possible version. But # since that's not expressible here, we make it >= the last *known* version to @@ -50,13 +50,13 @@ gem "chef-provisioning", ">= 2.0" gem "chef-provisioning-aws", ">= 2.0" gem "chef-provisioning-azure", ">= 0.6.0" gem "chef-provisioning-fog", ">= 0.20.0" gem "chef-provisioning-vagrant", ">= 0.11.0" - gem "chef-vault" + gem "chef-vault", "~> 2" # The chef version is pinned by "rake dependencies", which grabs the current version from omnibus. - gem "chef", github: "chef/chef", branch: "v12.19.36" + gem "chef", github: "chef/chef", branch: "v12.21.2" # Pinned cheffish to version 5.0.1 since the latest version 13.0.0 has # a dependency to ruby 2.3.3 but we are shipping ChefDK with ruby 2.3.1 # # TODO: Remove this pin once we have solve the problem gem "cheffish", "= 5.0.1" @@ -96,10 +96,10 @@ gem "winrm-elevated" gem "cucumber" # TODO Pinning these for now because github_changelog_generator has a bunch # of different versions across our products - gem "nokogiri", "~> 1.6.3" + gem "nokogiri", "~> 1.7.2" end # Everything except AIX and Windows group(:linux, :bsd, :mac_os_x, :solaris) do gem "ruby-shadow", platform: :ruby