version_policy.rb in chef-dk-0.14.25 vs version_policy.rb in chef-dk-0.15.9

@@ -46,10 +46,17 @@
   "libzmq" => "4.0.5",
 
   ## These can float as they are frequently updated in a way that works for us
   #override "cacerts" =>"???",
   #override "openssl" =>"???",
+
+  # We manually pin Delivery CLI right now. In the future we should have the bump
+  # bot automatically update this to the latest delivered version. We cannot look
+  # in Artifactory because in the future we will only be building Delivery CLI
+  # from the ChefDK. We cannot look at the Github tags because those are committed
+  # in the Build phase, and we only want to send customers Delivered changes.
+  "delivery-cli" => "0.0.21",
 }
 
 #
 # rake dependencies:update_omnibus_overrides (tasks/dependencies.rb) reads this
 # and modifies omnibus_overrides.rb
@@ -92,15 +99,16 @@
   # We have a task called update_stable_channel_gems which scans and pins to the
   # latest released chef/chef-config/opscode-pushy-client but it pulls from the
   # chef repo instead of from rubygems. Bundler currently considers any git
   # source at the same version (or lower) than one available from rubygems as
   # outdated and hence fails the outdated gem test, confusing Julia bot.
-  
+
   # Therefore..  turn checks on both of them off. If and when the rake task for
   # update_stable_channel_gems changes, this exclusion can be revisited.
   "chef",
   "chef-config",
   "opscode-pushy-client",
+  "nokogiri",
 ]
 
 #
 # Some gems are part of our bundle (must be installed) but not important
 # enough to lock. We allow `bundle install` in test-kitchen, berks, etc.