version_policy.rb in chef-dk-0.15.16 vs version_policy.rb in chef-dk-0.16.28

@@ -24,12 +24,12 @@
   "libiconv" => "1.14",
   "liblzma" => "5.2.2",
   ## according to comment in omnibus-sw, the very latest versions don't work on solaris
   # https://github.com/chef/omnibus-software/blob/aefb7e79d29ca746c3f843673ef5e317fa3cba54/config/software/libtool.rb#L23
   "libtool" => "2.4.2",
-  "libxml2" => "2.9.3",
-  "libxslt" => "1.1.28",
+  "libxml2" => "2.9.4",
+  "libxslt" => "1.1.29",
   "libyaml" => "0.1.6",
   "makedepend" => "1.0.5",
   "ncurses" => "5.9",
   "pkg-config-lite" => "0.28-1",
   "ruby" => "2.1.8",
@@ -87,10 +87,11 @@
   "slop", # deo removed in pry > 0.10.3
   "timers",
   "unicode-display_width",
   "varia_model",
   "httpclient",
+  "molinillo",
   # 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.
@@ -98,10 +99,10 @@
   # 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",
+  "mixlib-cli"
 ]
 
 #
 # 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.