bootboot 0.1.1 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: f0ffd98be99f6485f9c7480c1af03185884bc7a3
-  data.tar.gz: 9c2f985c296d6c1ea93c06a49437b9fd670a1ad8
+SHA256:
+  metadata.gz: 14236a9169a7dea04af00afeb9f53f20cd53e70d969944f12824ba98f76e525a
+  data.tar.gz: 9a31116c9844389ef5a40e234c15a6cdbfaaf031ed67ceaf47856dd2c3496fa7
 SHA512:
-  metadata.gz: 8992b0f398e049de5dc730d49f39ce35e908828168939583ff5d84362b6bc84d3193548c92f83117473a7887a6e5c22bb7d76c59aca0a52b3b9609b3dc518135
-  data.tar.gz: c4a6e8932482b1e5dd96f8e3e26e08de41e71f8cc38a0872d696a3702381073ad324440b3e95dde8709910907dfe0fa03937530e9a95287584ae82d6e43c33a3
+  metadata.gz: add7b5ca8aa44d3bed18fdcc09b61cf12cc02174a9b2dc947393e22592b0ffa6bea5c4409a8f70564f7d4b501c2233e65a6a292a24c549c915fdd817d46a65f9
+  data.tar.gz: 1114c2d69483098dab6180f7b7ed9b59aea471386c95be1df06ed38f242a021ee2fcf5a21181ebe6eb35a3b73e5b90cedbec26198d20716d4c1a3ee5b3861b0e

data/README.md

@@ -1,4 +1,4 @@
-## 👢👢 Bootboot
+## 👢👢 Bootboot   - [![Build Status](https://travis-ci.com/Shopify/bootboot.svg?branch=master)](https://travis-ci.com/Shopify/bootboot)
 
 Introduction
 ------------
@@ -40,25 +40,161 @@ No matter what approach you decide to take, you'll need to create tooling to ens
 
 Bootboot is only useful if you decide to follow the second approach. It creates the required tooling as well as the Bundler workaround needed to enable dual booting.
 
-
-
 Installation
 ------------
 1) In your Gemfile, add this
 ```ruby
-plugin 'bootboot', '~> 0.1.1`
+plugin 'bootboot', '~> 0.1.1'
 ```
 2) Run `bundle install && bundle bootboot`
 3) You're done. Commit the Gemfile and the Gemfile_next.lock
 
+Note: You should only run `bundle bootboot` once to install the plugin, otherwise your Gemfile will get updated each time you run it.
+
 Dual boot it!
 ------------
 If you want to boot using the dependencies from the `Gemfile_next.lock`, run any bundler command prefixed with the `DEPENDENCIES_NEXT=1` ENV variable. I.e. `DEPENDENCIES_NEXT=1 bundle exec irb`.
 
+**Note:** `bootboot` will use the gems and Ruby version specified per environment in your `Gemfile` to resolve dependencies and keep `Gemfile.lock` and `Gemfile_next.lock` in sync, but it does not do any magic to actually change the running Ruby version or install the gems in the environment you are not currently running, it simply tells Bundler which Ruby and gem versions to use in its resolution algorithm and keeps the lock files in sync. If you are a developer who is not involved in updating the dependency set, this should not affect you, simply use bundler normally. _However_, if you are involved in the dependency changes directly, you will often have to run `DEPENDENCIES_NEXT=1 bundle install` after making changes to the dependencies.
+
+```sh
+# This will update Gemfile.lock and Gemfile_next.lock and install the gems
+# specified in Gemfile.lock:
+$ bundle update some_gem
+# This will actually install the gems specified in Gemfile_next.lock
+$ DEPENDENCIES_NEXT=1 bundle install
+```
+
+Dual boot different Ruby versions
+---------------------------------
+
+While dual booting is often used for framework upgrades, it is also possible to use `bootboot` to dual boot two Ruby versions, each with its own set of gems.
+
+```ruby
+# Gemfile
+
+if ENV['DEPENDENCIES_NEXT']
+  ruby '2.6.5'
+else
+  ruby '2.5.7'
+end
+```
+
+Dual booting Ruby versions does incur some additional complications however, see the examples following for more detail.
+
+Example: updating a gem while dual booting Ruby versions
+--------------------------------------------------------
+
+To dual boot an app while upgrading from Ruby 2.5.7 to Ruby 2.6.5, your Gemfile would look like this:
+
+```ruby
+# Gemfile
+
+if ENV['DEPENDENCIES_NEXT']
+  ruby '2.6.5'
+else
+  ruby '2.5.7'
+end
+```
+
+After running `bundle install`, `Gemfile.lock` will have:
+
+```
+RUBY VERSION
+   ruby 2.5.7p206
+```
+
+and `Gemfile_next.lock` will have:
+
+```
+RUBY VERSION
+   ruby 2.6.5p114
+```
+Assuming there's a gem `some_gem` with the following constraints in its gemspecs:
 
-Keep` the Gemfile_next.lock` in sync
+```ruby
+# some_gem-1.0.gemspec
+spec.version = "1.0"
+spec.required_ruby_version = '>= 2.5.7'
+```
+
+```ruby
+# some_gem-2.0.gemspec
+spec.version = "2.0"
+spec.required_ruby_version = '>= 2.6.5'
+```
+
+Running `bundle update some_gem` will use Ruby 2.5.7 to resolve `some_gem` for `Gemfile.lock` and Ruby 2.6.5 to resolve `some_gem` for `Gemfile_next.lock` with the following results:
+
+Gemfile.lock:
+```
+specs:
+  some_gem (1.0)
+```
+
+Gemfile_next.lock:
+```
+specs:
+  some_gem (2.0)
+```
+
+**Note:** It is important to note that at this point, `some_gem 2.0` **will not** be installed on your system, it will simply be specified in `Gemfile_next.lock`, since installing it on the system would require changing the running Ruby version. This is sufficient to keep `Gemfile_next.lock` in sync, but is a potential source of confusion. To install gems under both versions of Ruby, see the next section.
+
+Vendoring both sets of gems
+---------------------------
+To vendor both sets of gems, make sure caching is enabled by checking `bundle config` or bundle gems using `bundle pack`.
+
+```bash
+bundle pack
+DEPENDENCIES_NEXT=1 bundle pack
+```
+
+### Example: running Ruby scripts while dual booting Ruby versions
+
+When running Ruby scripts while dual booting two different Ruby versions, you have to remember to do two things simultaneously for every command:
+- Run the command with the correct version of Ruby
+- Add the DEPENDENCIES_NEXT environment variable to tell bundler to use `Gemfile_next.lock`
+
+So to run a spec in both versions, the workflow would look like this (assuming chruby for version management):
+
+```sh
+$ chruby 2.5.7
+$ bundle exec rspec spec/some_spec.rb
+$ chruby 2.6.5
+$ DEPENDENCIES_NEXT=1 bundle exec rspec spec/some_spec.rb
+```
+
+Perhaps more importantly, to update or install a gem, the workflow would look like this:
+
+```sh
+# This will update Gemfile.lock and Gemfile_next.lock and install the gems
+# specified in Gemfile.lock:
+$ chruby 2.5.7
+$ bundle update some_gem
+# This will actually install the gems specified in Gemfile_next.lock under the
+# correct Ruby installation:
+$ chruby 2.6.5
+$ DEPENDENCIES_NEXT=1 bundle install
+```
+
+Configuration (Optional)
+------------------------
+By default Bootboot will use the `DEPENDENCIES_NEXT` environment variable to update your Gemfile_next.lock. You can however configure it. For example, if you want the dualboot to happen when the `SHOPIFY_NEXT` env variable is present, you simply have to add this in your Gemfile:
+
+```ruby
+# Gemfile
+Bundler.settings.set_local('bootboot_env_prefix', 'SHOPIFY')
+```
+
+Keep the `Gemfile_next.lock` in sync
 ------------
 When a developer bumps or adds a dependency, Bootboot will ensure that the `Gemfile_next.lock` snapshot gets updated.
 
 **However, this feature is only available if you are on Bundler `>= 1.17`**
 Other versions will trigger a warning message telling them that Bootboot can't automatically keep the `Gemfile_next.lock` in sync.
+
+If you use the deployment flag (`bundle --deployment`) this plugin won't work on Bundler `<= 2.0.1`. Consider using this workaround in your Gemfile for these versions of Bundler:
+
+```ruby
+plugin 'bootboot', '~> 0.1.2' unless Bundler.settings[:frozen]
+```

data/lib/bootboot/bundler_patch.rb

@@ -1,8 +1,10 @@
 # frozen_string_literal: true
 
+require "bootboot/ruby_source"
+
 module DefinitionPatch
   def initialize(wrong_lock, *args)
-    lockfile = if ENV['SKIP_BUNDLER_PATCH']
+    lockfile = if ENV["BOOTBOOT_UPDATING_ALTERNATE_LOCKFILE"]
       wrong_lock
     else
       Bootboot::GEMFILE_NEXT_LOCK
@@ -12,15 +14,48 @@ module DefinitionPatch
   end
 end
 
+module RubyVersionPatch
+  def system
+    if ENV["BOOTBOOT_UPDATING_ALTERNATE_LOCKFILE"]
+      # If we're updating the alternate file and the ruby version specified in
+      # the Gemfile is different from the Ruby version currently running, we
+      # want to write the version specified in `Gemfile` for the current
+      # dependency set to the lock file
+      Bundler::Definition.build(Bootboot::GEMFILE, nil, false).ruby_version || super
+    else
+      super
+    end
+  end
+end
+
+module DefinitionSourceRequirementsPatch
+  def source_requirements
+    super.tap do |source_requirements|
+      # Bundler has a hard requirement that Ruby should be in the Metadata
+      # source, so this replaces Ruby's Metadata source with our custom source
+      source = Bootboot::RubySource.new({})
+      source_requirements[source.ruby_spec_name] = source
+    end
+  end
+end
+
 module SharedHelpersPatch
   def default_lockfile
     Bootboot::GEMFILE_NEXT_LOCK
   end
 end
 
+Bundler::Definition.prepend(DefinitionSourceRequirementsPatch)
+Bundler::RubyVersion.singleton_class.prepend(RubyVersionPatch)
+
 Bundler::Dsl.class_eval do
   def enable_dual_booting
     Bundler::Definition.prepend(DefinitionPatch)
     Bundler::SharedHelpers.singleton_class.prepend(SharedHelpersPatch)
+    Bundler::Settings.prepend(Module.new do
+      def app_cache_path
+        "vendor/cache-next"
+      end
+    end)
   end
 end

data/lib/bootboot/command.rb

@@ -1,27 +1,27 @@
 # frozen_string_literal: true
 
-require 'fileutils'
+require "fileutils"
 
 module Bootboot
   class Command < Bundler::Plugin::API
     def setup
-      self.class.command('bootboot')
+      self.class.command("bootboot")
     end
 
     def exec(_cmd, _args)
       FileUtils.cp(GEMFILE_LOCK, GEMFILE_NEXT_LOCK)
 
-      File.open(GEMFILE, 'a+') do |f|
-        f.write(<<-EOM)
-Plugin.send(:load_plugin, 'bootboot') if Plugin.installed?('bootboot')
+      File.open(GEMFILE, "a+") do |f|
+        f.write(<<~EOM)
+          Plugin.send(:load_plugin, 'bootboot') if Plugin.installed?('bootboot')
 
-if ENV['DEPENDENCIES_NEXT']
-  enable_dual_booting if Plugin.installed?('bootboot')
+          if ENV['#{Bootboot.env_next}']
+            enable_dual_booting if Plugin.installed?('bootboot')
 
-  # Add any gem you want here, they will be loaded only when running
-  # bundler command prefixed with `#{DUALBOOT_NEXT}=1`.
-end
-EOM
+            # Add any gem you want here, they will be loaded only when running
+            # bundler command prefixed with `#{Bootboot.env_next}=1`.
+          end
+        EOM
       end
     end
   end

data/lib/bootboot/gemfile_next_auto_sync.rb

@@ -23,7 +23,7 @@ module Bootboot
     end
 
     def opt_in
-      self.class.hook('before-install-all') do
+      self.class.hook("before-install-all") do
         @previous_lock = Bundler.default_lockfile.read
       end
 
@@ -31,9 +31,9 @@ module Bootboot
         current_definition = Bundler.definition
 
         next if !GEMFILE_NEXT_LOCK.exist? ||
-                nothing_changed?(current_definition) ||
-                ENV[DUALBOOT_NEXT] ||
-                ENV[DUALBOOT_PREVIOUS]
+          nothing_changed?(current_definition) ||
+          ENV[Bootboot.env_next] ||
+          ENV[Bootboot.env_previous]
 
         update!(current_definition)
       end
@@ -48,8 +48,8 @@ module Bootboot
       lock = which_lock
 
       Bundler.ui.confirm("Updating the #{lock}")
-      ENV[env] = '1'
-      ENV['SKIP_BUNDLER_PATCH'] = '1'
+      ENV[env] = "1"
+      ENV["BOOTBOOT_UPDATING_ALTERNATE_LOCKFILE"] = "1"
 
       unlock = current_definition.instance_variable_get(:@unlock)
       definition = Bundler::Definition.build(GEMFILE, lock, unlock)
@@ -57,14 +57,14 @@ module Bootboot
       definition.lock(lock)
     ensure
       ENV.delete(env)
-      ENV.delete('SKIP_BUNDLER_PATCH')
+      ENV.delete("BOOTBOOT_UPDATING_ALTERNATE_LOCKFILE")
     end
 
     def which_env
       if Bundler.default_lockfile.to_s =~ /_next\.lock/
-        DUALBOOT_PREVIOUS
+        Bootboot.env_previous
       else
-        DUALBOOT_NEXT
+        Bootboot.env_next
       end
     end
 

data/lib/bootboot/ruby_source.rb

@@ -0,0 +1,39 @@
+# frozen_string_literal: true
+
+module Bootboot
+  class RubySource
+    include Bundler::Plugin::API::Source
+
+    # The spec name for Ruby changed from "ruby\0" to "Ruby\0" between Bundler
+    # 1.17 and 2.0, so we want to use the Ruby spec name from Metadata so
+    # Bootboot works across Bundler versions
+    def ruby_spec_name
+      @ruby_spec_name ||= begin
+        metadata = Bundler::Source::Metadata.new
+        ruby_spec = metadata.specs.find { |s| s.name[/[R|r]uby\0/] }
+        # Default to Bundler > 2 in case the Bundler internals change
+        ruby_spec ? ruby_spec.name : "Ruby\0"
+      end
+    end
+
+    def specs
+      Bundler::Index.build do |idx|
+        # If the ruby version specified in the Gemfile is different from the
+        # Ruby version currently running, we want to build a definition without
+        # a lockfile (so that `ruby_version` in the Gemfile isn't overridden by
+        # the lockfile) and get its `ruby_version`. This will be used both
+        # during dependency resolution so that we can pretend the intended Ruby
+        # version is present, as well as when updating the lockfile itself.
+        ruby_version = Bundler::Definition.build(Bootboot::GEMFILE, nil, false).ruby_version
+        ruby_version ||= Bundler::RubyVersion.system
+        ruby_spec = Gem::Specification.new(ruby_spec_name, ruby_version.gem_version)
+        ruby_spec.source = self
+        idx << ruby_spec
+      end
+    end
+
+    def to_s
+      "Bootboot plugin Ruby source"
+    end
+  end
+end

data/lib/bootboot/version.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module Bootboot
-  VERSION = "0.1.1"
+  VERSION = "0.2.1"
 end

data/lib/bootboot.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 require "bootboot/version"
 require "bootboot/bundler_patch"
 
@@ -5,11 +7,25 @@ module Bootboot
   GEMFILE = Bundler.default_gemfile
   GEMFILE_LOCK = Pathname("#{GEMFILE}.lock")
   GEMFILE_NEXT_LOCK = Pathname("#{GEMFILE}_next.lock")
-  DUALBOOT_NEXT = 'DEPENDENCIES_NEXT'
-  DUALBOOT_PREVIOUS = 'DEPENDENCIES_PREVIOUS'
 
-  autoload :GemfileNextAutoSync, 'bootboot/gemfile_next_auto_sync'
-  autoload :Command,             'bootboot/command'
+  autoload :GemfileNextAutoSync, "bootboot/gemfile_next_auto_sync"
+  autoload :Command,             "bootboot/command"
+
+  class << self
+    def env_next
+      env_prefix + "_NEXT"
+    end
+
+    def env_previous
+      env_prefix + "_PREVIOUS"
+    end
+
+    private
+
+    def env_prefix
+      Bundler.settings["bootboot_env_prefix"] || "DEPENDENCIES"
+    end
+  end
 end
 
 Bootboot::GemfileNextAutoSync.new.setup

metadata

@@ -1,29 +1,29 @@
 --- !ruby/object:Gem::Specification
 name: bootboot
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.2.1
 platform: ruby
 authors:
 - Shopify
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-11-20 00:00:00.000000000 Z
+date: 2022-04-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: bundler
+  name: minitest
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.17'
+        version: '5.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.17'
+        version: '5.0'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
@@ -38,46 +38,27 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '10.0'
-- !ruby/object:Gem::Dependency
-  name: minitest
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '5.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '5.0'
-description: " This gems removes you the overhead of monkeypatching your Gemfile in
-  order to dualboot your app using the Gemfile_next lock strategy It also ensure that
-  dependencies in the Gemfile lock and Gemfile_next lock are in sync whenever someone
-  updates a gem "
+description: " This gem remove the overhead of monkeypatching your Gemfile in order
+  to dualboot your app using the Gemfile_next lock strategy It also ensure that dependencies
+  in the Gemfile lock and Gemfile_next lock are in sync whenever someone updates a
+  gem "
 email:
 - rails@shopify.com
 executables: []
 extensions: []
-extra_rdoc_files: []
+extra_rdoc_files:
+- LICENSE.txt
+- README.md
 files:
-- ".gitignore"
-- ".travis.yml"
-- Gemfile
-- Gemfile.lock
 - LICENSE.txt
 - README.md
-- Rakefile
-- bin/console
-- bootboot.gemspec
 - lib/bootboot.rb
 - lib/bootboot/bundler_patch.rb
 - lib/bootboot/command.rb
 - lib/bootboot/gemfile_next_auto_sync.rb
+- lib/bootboot/ruby_source.rb
 - lib/bootboot/version.rb
 - plugins.rb
-- shipit.rubygems.yml
 homepage: https://github.com/shopify/bootboot
 licenses:
 - MIT
@@ -85,6 +66,7 @@ metadata:
   homepage_uri: https://github.com/shopify/bootboot
   source_code_uri: https://github.com/shopify/bootboot
   changelog_uri: https://github.com/Shopify/bootboot/blob/master/CHANGELOG.md
+  allowed_push_host: https://rubygems.org
 post_install_message: 
 rdoc_options: []
 require_paths:
@@ -100,8 +82,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.6.14
+rubygems_version: 3.2.20
 signing_key: 
 specification_version: 4
 summary: Dualbooting your ruby app made easy.

data/.gitignore

@@ -1,8 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/

data/.travis.yml

@@ -1,7 +0,0 @@
-sudo: false
-cache: bundler
-language: ruby
-before_install:
-  - gem update bundler
-notifications:
-  email: false

data/Gemfile

@@ -1,10 +0,0 @@
-source "https://rubygems.org"
-
-git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
-
-gemspec
-
-group :deployment do
-  gem 'package_cloud'
-  gem 'rake'
-end

data/Gemfile.lock

@@ -1,49 +0,0 @@
-PATH
-  remote: .
-  specs:
-    bootboot (0.1.1)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    domain_name (0.5.20180417)
-      unf (>= 0.0.5, < 1.0.0)
-    highline (1.6.20)
-    http-cookie (1.0.3)
-      domain_name (~> 0.5)
-    json_pure (1.8.1)
-    mime-types (3.2.2)
-      mime-types-data (~> 3.2015)
-    mime-types-data (3.2018.0812)
-    minitest (5.11.3)
-    netrc (0.11.0)
-    package_cloud (0.3.05)
-      highline (= 1.6.20)
-      json_pure (= 1.8.1)
-      rainbow (= 2.2.2)
-      rest-client (~> 2.0)
-      thor (~> 0.18)
-    rainbow (2.2.2)
-      rake
-    rake (10.5.0)
-    rest-client (2.0.2)
-      http-cookie (>= 1.0.2, < 2.0)
-      mime-types (>= 1.16, < 4.0)
-      netrc (~> 0.8)
-    thor (0.20.3)
-    unf (0.1.4)
-      unf_ext
-    unf_ext (0.0.7.5)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bootboot!
-  bundler (~> 1.17)
-  minitest (~> 5.0)
-  package_cloud
-  rake
-
-BUNDLED WITH
-   1.17.1

data/Rakefile

@@ -1,10 +0,0 @@
-require "bundler/gem_tasks"
-require "rake/testtask"
-
-Rake::TestTask.new(:test) do |t|
-  t.libs << "test"
-  t.libs << "lib"
-  t.test_files = FileList["test/**/*_test.rb"]
-end
-
-task :default => :test

data/bin/console

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "bootboot"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bootboot.gemspec

@@ -1,33 +0,0 @@
-lib = File.expand_path("../lib", __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require "bootboot/version"
-
-Gem::Specification.new do |spec|
-  spec.name          = "bootboot"
-  spec.version       = Bootboot::VERSION
-  spec.authors       = ["Shopify"]
-  spec.email         = ["rails@shopify.com"]
-
-  spec.summary       = "Dualbooting your ruby app made easy."
-  spec.description   = <<-EOM.gsub(/\W+/, ' ')
-    This gems removes you the overhead of monkeypatching your Gemfile in order to
-    dualboot your app using the Gemfile_next.lock strategy.
-    It also ensure that dependencies in the Gemfile.lock and Gemfile_next.lock are
-    in sync whenever someone updates a gem.
-  EOM
-  spec.homepage      = "https://github.com/shopify/bootboot"
-  spec.license       = "MIT"
-
-  spec.metadata["homepage_uri"] = spec.homepage
-  spec.metadata["source_code_uri"] = "https://github.com/shopify/bootboot"
-  spec.metadata["changelog_uri"] = "https://github.com/Shopify/bootboot/blob/master/CHANGELOG.md"
-
-  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
-  end
-  spec.require_paths = ["lib"]
-
-  spec.add_development_dependency "bundler", "~> 1.17"
-  spec.add_development_dependency "rake", "~> 10.0"
-  spec.add_development_dependency "minitest", "~> 5.0"
-end

data/shipit.rubygems.yml

@@ -1 +0,0 @@
-# Default config