jacobthemyth
commented
4 years ago - Update development bundler to 2.1.4, which is currently the latest version of bundler. There is no particular reason this version of bundler was chosen, but in order to fix Travis (see next), the most straightforward solution was to install a specific bundler version on Travis, and it seemed that the latest version was the most obvious choice.
- The Ruby and bundler versions were not specified for Travis, so the fact that Gemfile.lock required a specific version of bundler was causing errors in CI. This PR pins the Ruby and bundler versions so that the Gemfile.lock matches what is installed. If it is desired, Travis also supports running multiple dependency sets so that bootboot could be run against many versions of bundler.
- Remove bundler from gemspec. Since the version of bundler is pinned in Gemfile.lock, it isn't necessary to specify bundler as a development dependency, and removing it removes the duplication of versions between Gemfile.lock and the gemspec. Maybe it makes sense to have this in the gemspec though, it just seemed unecessary since in almost all cases, bundler will have to be installed already to resolve the gemspec.
- Update a deprecated API