What's New in each Release
The Bundler 1.13 announcement includes context and a more detailed explanation of the changes in this version. This is a summary of the biggest changes. As always, a detailed list of every change is provided in the changelog.
doctor command for automated troubleshooting. So far, it can automatically detect gems that have been compiled against libraries that no longer exist, and compile them again to fix them.
Gems that declare a
required_ruby_version will now resolve correctly as long as your Gemfile contains a
ruby declaration. If a gem cannot be resolved because of your Ruby version, the error will correctly indicate that your Ruby version conflicts with your other gem version requirements.
Manage locked platforms
In the past, the only way to resolve your Gemfile on a new platform (like
mswin) was to run
bundle install on that platform. We've added explicit options to the
lock command to allow managing platforms. Platforms can be added using
bundle lock --add-platform NAME, and platforms can be removed using
bundle lock --remove-platform NAME.
Fine controls for the
updatecommand now has several options to enable users to fine-tune exactly what it is that they will get, using the new flags
--strict. It was also recently pointed out to us that running
updatecould even result in some locked gems being changed to an older version! We can’t change the default behavior to avoid that until version 2.0, but for now we’ve added a config setting. To prevent the
updatecommand from ever “upgrading” you to an older version, run
bundle config only_update_to_newer_versions true.
Experimental plugin system
The plugin system also supports "source" plugins, which means it should be possible to use gems from Subversion, Mercurial, S3, or anything else you can think of. In addition to source plugins, we've started adding new "lifecycle" hooks. That means plugins will be able to hook in and run their own code before, during, or after the install or update process.
Experimental Bundler version locking
automatically trampoline to the bundler version locked in the lockfile, only updating to the running version on
bundle update --bundler (@segiddins)
- Support for RubyGems 2.6.4
- Automatic gem installation for
- Dramatic resolver optimizations
- Better load-based
- Support for setting "mirror" servers by hostname
- Automatic retrying for gem downloads