Gemfile.lock in optimizely_server_side-0.0.17 vs Gemfile.lock in optimizely_server_side-0.0.18

- old
+ new

@@ -1,24 +1,24 @@ PATH remote: . specs: - optimizely_server_side (0.0.16) - activesupport (~> 4.2, >= 4.2.6) + optimizely_server_side (0.0.18) + activesupport (>= 4.2.6) optimizely-sdk (= 0.1.1) GEM remote: https://rubygems.org/ specs: - activesupport (4.2.7.1) + activesupport (5.0.0.1) + concurrent-ruby (~> 1.0, >= 1.0.2) i18n (~> 0.7) - json (~> 1.7, >= 1.7.7) minitest (~> 5.1) - thread_safe (~> 0.3, >= 0.3.4) tzinfo (~> 1.1) addressable (2.3.8) codeclimate-test-reporter (0.6.0) simplecov (>= 0.7.1, < 1.0.0) + concurrent-ruby (1.0.2) crack (0.4.3) safe_yaml (~> 1.0.0) diff-lcs (1.2.5) docile (1.1.5) hashdiff (0.3.0) @@ -27,11 +27,11 @@ multi_xml (>= 0.5.2) i18n (0.7.0) json (1.8.3) json-schema (2.6.2) addressable (~> 2.3.8) - minitest (5.9.0) + minitest (5.9.1) multi_xml (0.5.5) murmurhash3 (0.1.6) optimizely-sdk (0.1.1) httparty (~> 0.13.7) json-schema (~> 2.6.2) @@ -71,6 +71,6 @@ optimizely_server_side! rspec (~> 3.5) webmock (~> 2.1) BUNDLED WITH - 1.12.5 + 1.13.6