v2.0.0

Breaking Changes:

• Dropped support for versions of Ruby < 2.3
• Dropped support for version of RubyGems < 3.0.0
• :github source in the Gemfile now defaults to using HTTPS
• Moved error messages from STDOUT to STDERR
• Bundler now auto-switches between version 1 and 2 based on the Lockfile

v2.0.0.pre.3

Breaking Changes:

• Bundler 2 now requires RubyGems 3.0.0 at minimum

Changes:

• Ruby 2.6 compatibility fixes (@segiddins)
• Import changes from Bundler 1.17.3 release

Note: To upgrade your Gemfile to Bundler 2 you will need to run bundle update --bundler

v1.17.3

Bugfixes:

• Fix a Bundler error when installing gems on old versions of RubyGems (#6839, @colby-swandale)
• Fix a rare issue where Bundler was removing itself after a bundle clean (#6829, @colby-swandale)

Documentation:

• Add entry for the bundle remove command to the main Bundler manual page

v1.17.2

Changes:

• Add compatibility for bundler merge with Ruby 2.6

v2.0.0.pre.2

Breaking Changes:

• :github source in the Gemfile now defaults to using HTTPS

Changes

• Add compatibility for Bundler merge into ruby-src

Note: To upgrade your Gemfile to Bundler 2 you will need to run bundle update --bundler

v2.0.0.pre.1

Breaking Changes:

• Dropped support for versions of Ruby < 2.3
• Dropped support for version of RubyGems < 2.5
• Moved error messages from STDOUT to STDERR

Note: To upgrade your Gemfile to Bundler 2 you will need to run bundle update --bundler

v1.17.1

Convert Pathnames to Strings before sorting them, fixing #6760 and #6758 (#6761, @alexggordon)

v1.17.0

Features:

• Configure Bundler home, cache, config and plugin directories with BUNDLE_USER_HOME, BUNDLE_USER_CACHE, BUNDLE_USER_CONFIG and BUNDLE_USER_PLUGIN env vars (#4333, @gwerbin)
• Add --all option to bundle binstubs that will generate an executable file for all gems with commands in the bundle
• Add bundle remove command to remove gems from the Gemfile via the CLI
• Improve checking file permissions and asking for sudo in Bundler when it doesn't need to
• Add error message to bundle add to check adding duplicate gems to the Gemfile
• When asking for sudo, Bundler will show a list of folders/files that require elevated permissions to write to.
• Check folder/file permissions of the Bundle home directory in the bundle doctor command (#5786, @ajwann)
• Remove compiled gem extensions when running bundle clean (#5596, @akhramov)
• Add --paths option to bundle list command (#6172, @colby-swandale)
• Add base error class to gems generated from bundle gem (#6260, @christhekeele)
• Correctly re-install gem extensions with a git source when running bundle pristine (#6294, @wagenet)
• Add config option to disable platform warnings (#6124, @agrim123)
• Add --skip-install option to bundle add command to add gems to the Gemfile without installation (#6511, @agrim123)
• Add --only-explicit option to bundle outdated to list only outdated gems in the Gemfile (#5366, @peret)
• Support adding multiple gems to the Gemfile with bundle add (#6543, @agrim123)
• Make registered plugin events easier to manage in the Plugin API (@jules2689)
• Add new gem install hooks to the Plugin API (@jules2689)
• Add --optimistic and --strict options to bundle add (#6553, @agrim123)
• Add --without-group and --only-group options to bundle list (#6564, @agrim123)
• Add --gemfile option to the bundle exec command (#5924, @ankitkataria)

The following new features are available but are not enabled by default. These are intended to be tested by users for the upcoming release of Bundler 2.

• Make install --path relative to the current working directory (#2048, @igorbozato)
• Auto-configure job count (#5808, @segiddins)
• Use the Gem Version Promoter for major gem updates (#5993, @segiddins)
• Add config option to add the Ruby scope to bundle config path when configured globally (@segiddins)
• Improve deprecation warning message for bundle show command
• Improve deprecation warning message for the --force option in bundle install

v1.17.0.pre.2

Features:

• Configure Bundler home, cache, config and plugin directories with BUNDLE_USER_HOME, BUNDLE_USER_CACHE, BUNDLE_USER_CONFIG and BUNDLE_USER_PLUGIN env vars (#4333, @gwerbin)
• Add --all option to bundle binstubs that will generate an executable file for all gems with commands in the bundle
• Add bundle remove command to remove gems from the Gemfile via the CLI
• Improve checking file permissions and asking for sudo in Bundler when it doesn't need to
• Add error message to bundle add to check adding duplicate gems to the Gemfile
• When asking for sudo, Bundler will show a list of folders/files that require elevated permissions to write to.

The following new features are available but are not enabled by default. These are intended to be tested by users for the upcoming release of Bundler 2.

• Improve deprecation warning message for bundle show command
• Improve deprecation warning message for the --force option in bundle install

v1.16.6

Changes:

• Add an error message when adding a gem with bundle add that's already in the bundle (#6341, @agrim123)
• Add Homepage, Source Code and Changelog URI metadata fields to the bundle gem gemspec template (@walf443)

Bugfixes:

• Fix issue where updating a gem resulted in the gem's version being downgraded when BUNDLE_ONLY_UPDATE_TO_NEWER_VERSIONS was set (#6529, @theflow)
• Fix some rescue calls that don't specifiy error type (@utilum)
• Fix an issue when the Lockfile would contain platform-specific gems that it didn't need (#6491, @segiddins)
• Improve handling of adding new gems with only a single group to the Gemfile in bundle add (@agrim123)
• Refactor check for OpenSSL in bundle env (@voxik)
• Remove an unnecessary assignment in Metadata (@voxik)

Documentation:

• Update docs to reflect revised guidance to check in Gemfile.lock into version control for gems (#5879, @arbonap)
• Add documentation for the --all flag in bundle update (@agrim123)
• Update README to use bundle add in usage examples (@hdf1986)