Gemfile.lock in ae_easy-0.0.3 vs Gemfile.lock in ae_easy-0.0.4

- old
+ new

@@ -1,27 +1,44 @@ PATH remote: . specs: - ae_easy (0.0.3) + ae_easy (0.0.4) + ae_easy-config ae_easy-core + ae_easy-router + ae_easy-text GEM remote: https://rubygems.org/ + remote: https://Q34T4-cZG2rRRuLMNmG2zvwZsIJl7W5g@gem.fury.io/answersengine/ specs: - ae_easy-core (0.0.4) - answersengine (>= 0.2.25) + ae_easy-config (0.0.1) + ae_easy-core + ae_easy-core (0.1.0) + answersengine (>= 0.2.32) + faker + ae_easy-router (0.0.1) + ae_easy-config + ae_easy-core + ae_easy-text (0.0.1) + ae_easy-core ansi (1.5.0) - answersengine (0.2.31) + answersengine (0.2.33) httparty (~> 0.16.2) nokogiri (~> 1.6, < 1.10) thor (~> 0.20.3) - byebug (10.0.2) + byebug (11.0.0) + concurrent-ruby (1.1.4) docile (1.3.1) + faker (1.9.3) + i18n (>= 0.7) hirb (0.7.3) httparty (0.16.4) mime-types (~> 3.0) multi_xml (>= 0.5.2) - json (2.1.0) + i18n (1.5.3) + concurrent-ruby (~> 1.0) + json (2.2.0) mime-types (3.2.2) mime-types-data (~> 3.2015) mime-types-data (3.2018.0812) mini_portile2 (2.4.0) minitest (5.11.3)