Features:

• Add support for new default gems. In particular,

  • open3 #7455
  • cgi: #7456
  • uri #7460

  plus other PRs removing or lazily loading usages of these gems from other places to not interfere with user's choice, such as #7471 or #7473

Bugfixes:

• Fix bundle exec rake install failing #7474
• Fix bundle exec'ing to rubygems being silent #7442
• Restore previous BUNDLE_GEMFILE in bundler/inline #7418
• Fix error when using gem DSL's :glob option for selecting gemspecs from a specific source #7419

Changes:

• bundle config no longer warns when using "old interface" (might be deprecated again in the future) #7475
• bundle update no longer warns when used without arguments (might be deprecated again in the future) #7475

2.1.0.pre.3 (November 12, 2019)

Features:

• Add caller information to some deprecation messages to make them easier to fix #7361
• Reconcile bundle cache vs bundle package everywhere. Now in docs, CLI help and everywhere else bundle cache is the preferred version and bundle package remains as an alias #7389
• Display some basic bundler documentation together with ruby's RDoc based documentation #7394

Bugfixes:

• Fix typos deprecation message and upgrading docs #7374
• Deprecation warnings about taint usage on ruby 2.7 #7385
• Fix --help flag not correctly delegating to man when used with command aliases #7388
• bundle add should cache newly added gems if an application cache exists #7393
• Stop using an insecure folder as a "fallback home" when user home is not defined #7416
• Fix bundler/inline warning about Bundler.root redefinition #7417

2.1.0.pre.2 (September 15, 2019)

Bugfixes:

• Fix bundle clean trying to delete non-existent directory (#7340)
• Fix warnings about keyword argument separation on ruby 2.7 (#7337)

2.1.0.pre.1 (August 28, 2019)

One of the biggest changes in bundler 2.1.0 is that deprecations for upcoming breaking changes in bundler 3 will be turned on by default. We do this to grab feedback and communicate early to our users the kind of changes we're intending to ship with bundler 3. See #6965.

Another important improvement is a better coexistence between bundler installations and the default copy of bundler that comes with ruby installed as a default gem. Since bundler is shipped as a default gem with ruby, a number of users have been affected by issues where bundler ends up failing due to version mismatches, because at some point of the execution, bundler switches to run the default copy instead of the expected version. A number of PRs have been focused on minimizing (hopefully eliminating) this, such as #7100, #7137, #6996, #7056, #7062, #7193, #7216, #7274

Deprecations:

• See the the upgrading document for a detailed explanation of the deprecations that are getting enabled in bundler 2.1, and the future breaking changes in bundler 3.

Features:

• Reimplement config command using subcommands (#5981)
• Add bundle plugin list command (#6120)
• Introduce a bundle lock --gemfile flag (#6748)
• Add local git repository source option (--local_git) to plugin installation (#6749)
• Add quiet flag to inline bundler (#6828)
• Introduce a prefer_patch configuration that makes bundle update behave like bundle update --patch (#6931)
• Introduce Bundler.original_system and Bundler.original_exec to shell out or exec to external programs using the original environment before bundler was loaded (#7052)
• Add feature parity to bundle info GEM with respect to the old deprecated command

Bugfixes:

• Raise when the same gem is available in multiple sources, and show a suggestion to solve it (#5985)
• Validate that bundler has permissions to write to the tmp directory, and raise with a meaningful error otherwise (#5954)
• Remove downloaded .gem file from the cache if it's corrupted (#6010)
• Fix generated README in new gems to explicitly suggest running bundle install, so that the outcome is independent from the major version of bundler being run (#6068)
• Fix bundle outdated --group NAME when the group is listed second in the Gemfile (#6116)
• Improve conflict resolution messages by not calling "ruby" a gem when conflict happens in the required_ruby_version, and by filtering out requirements that didn't contribute to the conflict (#6647)
• Avoid fetching and rebuilding git gems whenever any gem is changed in the Gemfile (#6711)

Documentation:

• Fix typo on a file extension in bundle.ronn #7146
• Fix incorrect default value for cache_path configuration (#7229)
• Binstubs documentation has been improved (#5889)
• Fix incorrect sections when explaining :git, :branch, and :ref options (#7265)
• Fix mentions to remembered options in docs to explain the current state (#7242)

Internally, there's also been a bunch of improvements in our development environment, test suite, policies, contributing docs, and a bunch of cleanups of old compatibility code.