Releases: rubygems/bundler
v2.1.4
Bugfixes:
- Fix
net-http-pipelineno longer being allowed in Gemfiles if already installed in the system due to our vendored version ofnet-http-persistentoptionally requiring it #7529 - Fix inline gems no longer being requirable if no Gemfile is present in the directory hierarchy #7537
2.1.3 (January 2, 2020)
Bugfixes:
- Fix
rake buildwhen path has spaces on it #7514 - Fix
rake releasegit push tasks when the running shell hasgitas an alias of another command (likehub) #7510 - Fix some circular require warnings #7520
- Fix
bundle config set deployment truerecommended alternative tobundle config --deploymentto behave in the same way as the--deploymentflag #7519
2.1.2 (December 20, 2019)
Bugfixes:
- Restore an explicit
require "rubygems"on toprubygems_integration.rbto avoid some missing constant errors under some convoluted setups #7505
2.1.1 (December 17, 2019)
Bugfixes:
- Fix some cases of shelling out to
rubygemsstill being silent #7493 - Restore compatibility with
rubygems-bundlerso that binstubs work underRVM#7498
2.1.0 (December 15, 2019)
Features:
-
Add support for new default gems. In particular,
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 installfailing #7474 - Fix
bundle exec'ing to rubygems being silent #7442 - Restore previous
BUNDLE_GEMFILEinbundler/inline#7418 - Fix error when using
gemDSL's:globoption for selecting gemspecs from a specific source #7419
Changes:
bundle configno longer warns when using "old interface" (might be deprecated again in the future) #7475bundle updateno 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 cachevsbundle packageeverywhere. Now in docs, CLI help and everywhere elsebundle cacheis the preferred version andbundle packageremains as an alias #7389 - Display some basic
bundlerdocumentation together with ruby's RDoc based documentation #7394
Bugfixes:
- Fix typos deprecation message and upgrading docs #7374
- Deprecation warnings about
taintusage on ruby 2.7 #7385 - Fix
--helpflag not correctly delegating tomanwhen used with command aliases #7388 bundle addshould 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/inlinewarning aboutBundler.rootredefinition #7417
2.1.0.pre.2 (September 15, 2019)
Bugfixes:
- Fix
bundle cleantrying 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s [#6728](https://github.com/...
v2.1.3
Bugfixes:
- Fix
rake buildwhen path has spaces on it #7514 - Fix
rake releasegit push tasks when the running shell hasgitas an alias of another command (likehub) #7510 - Fix some circular require warnings #7520
- Fix
bundle config set deployment truerecommended alternative tobundle config --deploymentto behave in the same way as the--deploymentflag #7519
2.1.2 (December 20, 2019)
Bugfixes:
- Restore an explicit
require "rubygems"on toprubygems_integration.rbto avoid some missing constant errors under some convoluted setups #7505
2.1.1 (December 17, 2019)
Bugfixes:
- Fix some cases of shelling out to
rubygemsstill being silent #7493 - Restore compatibility with
rubygems-bundlerso that binstubs work underRVM#7498
2.1.0 (December 15, 2019)
Features:
-
Add support for new default gems. In particular,
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 installfailing #7474 - Fix
bundle exec'ing to rubygems being silent #7442 - Restore previous
BUNDLE_GEMFILEinbundler/inline#7418 - Fix error when using
gemDSL's:globoption for selecting gemspecs from a specific source #7419
Changes:
bundle configno longer warns when using "old interface" (might be deprecated again in the future) #7475bundle updateno 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 cachevsbundle packageeverywhere. Now in docs, CLI help and everywhere elsebundle cacheis the preferred version andbundle packageremains as an alias #7389 - Display some basic
bundlerdocumentation together with ruby's RDoc based documentation #7394
Bugfixes:
- Fix typos deprecation message and upgrading docs #7374
- Deprecation warnings about
taintusage on ruby 2.7 #7385 - Fix
--helpflag not correctly delegating tomanwhen used with command aliases #7388 bundle addshould 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/inlinewarning aboutBundler.rootredefinition #7417
2.1.0.pre.2 (September 15, 2019)
Bugfixes:
- Fix
bundle cleantrying 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s #6728
- Make
bundle cleanalso clean native extensions for gems with a git source #7058 - Fix
bundle info bundlerto show the correct path to the bundler gem #7026 - Fix
bundle config build.<gem>not sending multiple parameters toextconf.rbcorrectly [#7023](https://github.com/bundler/bundl...
v2.1.2
Bugfixes:
- Restore an explicit
require "rubygems"on toprubygems_integration.rbto avoid some missing constant errors under some convoluted setups #7505
2.1.1 (December 17, 2019)
Bugfixes:
- Fix some cases of shelling out to
rubygemsstill being silent #7493 - Restore compatibility with
rubygems-bundlerso that binstubs work underRVM#7498
2.1.0 (December 15, 2019)
Features:
-
Add support for new default gems. In particular,
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 installfailing #7474 - Fix
bundle exec'ing to rubygems being silent #7442 - Restore previous
BUNDLE_GEMFILEinbundler/inline#7418 - Fix error when using
gemDSL's:globoption for selecting gemspecs from a specific source #7419
Changes:
bundle configno longer warns when using "old interface" (might be deprecated again in the future) #7475bundle updateno 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 cachevsbundle packageeverywhere. Now in docs, CLI help and everywhere elsebundle cacheis the preferred version andbundle packageremains as an alias #7389 - Display some basic
bundlerdocumentation together with ruby's RDoc based documentation #7394
Bugfixes:
- Fix typos deprecation message and upgrading docs #7374
- Deprecation warnings about
taintusage on ruby 2.7 #7385 - Fix
--helpflag not correctly delegating tomanwhen used with command aliases #7388 bundle addshould 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/inlinewarning aboutBundler.rootredefinition #7417
2.1.0.pre.2 (September 15, 2019)
Bugfixes:
- Fix
bundle cleantrying 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s #6728
- Make
bundle cleanalso clean native extensions for gems with a git source #7058 - Fix
bundle info bundlerto show the correct path to the bundler gem #7026 - Fix
bundle config build.<gem>not sending multiple parameters toextconf.rbcorrectly #7023 - Fix bad error message on Gemfile errors under ruby 2.7 (still unreleased, but it's a bugfix for beta testers after all) #7038
- Warn about situations where multiple gems provide the same executable (#7075)
- Ignore
frozensetting in inline mode (#7125) - Fix incorrect "bundler attempted to update GEM but version stayed the same" message when updating git sourced gems (#6325)
- Don't check f...
v2.1.1
Bugfixes:
- Fix some cases of shelling out to
rubygemsstill being silent #7493 - Restore compatibility with
rubygems-bundlerso that binstubs work underRVM#7498
2.1.0 (December 15, 2019)
Features:
-
Add support for new default gems. In particular,
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 installfailing #7474 - Fix
bundle exec'ing to rubygems being silent #7442 - Restore previous
BUNDLE_GEMFILEinbundler/inline#7418 - Fix error when using
gemDSL's:globoption for selecting gemspecs from a specific source #7419
Changes:
bundle configno longer warns when using "old interface" (might be deprecated again in the future) #7475bundle updateno 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 cachevsbundle packageeverywhere. Now in docs, CLI help and everywhere elsebundle cacheis the preferred version andbundle packageremains as an alias #7389 - Display some basic
bundlerdocumentation together with ruby's RDoc based documentation #7394
Bugfixes:
- Fix typos deprecation message and upgrading docs #7374
- Deprecation warnings about
taintusage on ruby 2.7 #7385 - Fix
--helpflag not correctly delegating tomanwhen used with command aliases #7388 bundle addshould 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/inlinewarning aboutBundler.rootredefinition #7417
2.1.0.pre.2 (September 15, 2019)
Bugfixes:
- Fix
bundle cleantrying 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s #6728
- Make
bundle cleanalso clean native extensions for gems with a git source #7058 - Fix
bundle info bundlerto show the correct path to the bundler gem #7026 - Fix
bundle config build.<gem>not sending multiple parameters toextconf.rbcorrectly #7023 - Fix bad error message on Gemfile errors under ruby 2.7 (still unreleased, but it's a bugfix for beta testers after all) #7038
- Warn about situations where multiple gems provide the same executable (#7075)
- Ignore
frozensetting in inline mode (#7125) - Fix incorrect "bundler attempted to update GEM but version stayed the same" message when updating git sourced gems (#6325)
- Don't check for existence of a writable home directory if
BUNDLE_USER_HOMEis set (#6885) - Fix error message when server would respond to a bad username/password requiest with a 401 ([#6928](https://gi...
v2.1.0
Features:
-
Add support for new default gems. In particular,
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 installfailing #7474 - Fix
bundle exec'ing to rubygems being silent #7442 - Restore previous
BUNDLE_GEMFILEinbundler/inline#7418 - Fix error when using
gemDSL's:globoption for selecting gemspecs from a specific source #7419
Changes:
bundle configno longer warns when using "old interface" (might be deprecated again in the future) #7475bundle updateno 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 cachevsbundle packageeverywhere. Now in docs, CLI help and everywhere elsebundle cacheis the preferred version andbundle packageremains as an alias #7389 - Display some basic
bundlerdocumentation together with ruby's RDoc based documentation #7394
Bugfixes:
- Fix typos deprecation message and upgrading docs #7374
- Deprecation warnings about
taintusage on ruby 2.7 #7385 - Fix
--helpflag not correctly delegating tomanwhen used with command aliases #7388 bundle addshould 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/inlinewarning aboutBundler.rootredefinition #7417
2.1.0.pre.2 (September 15, 2019)
Bugfixes:
- Fix
bundle cleantrying 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s #6728
- Make
bundle cleanalso clean native extensions for gems with a git source #7058 - Fix
bundle info bundlerto show the correct path to the bundler gem #7026 - Fix
bundle config build.<gem>not sending multiple parameters toextconf.rbcorrectly #7023 - Fix bad error message on Gemfile errors under ruby 2.7 (still unreleased, but it's a bugfix for beta testers after all) #7038
- Warn about situations where multiple gems provide the same executable (#7075)
- Ignore
frozensetting in inline mode (#7125) - Fix incorrect "bundler attempted to update GEM but version stayed the same" message when updating git sourced gems (#6325)
- Don't check for existence of a writable home directory if
BUNDLE_USER_HOMEis set (#6885) - Fix error message when server would respond to a bad username/password requiest with a 401 (#6928)
- Fix
bundle outdatedpluralization when multiple groups are requested (#7063) - Fix
bundle installnot updating conservatively when gemspec is changed (#7143)
...
v2.1.0.pre.3
Features:
- Add caller information to some deprecation messages to make them easier to fix #7361
- Reconcile
bundle cachevsbundle packageeverywhere. Now in docs, CLI help and everywhere elsebundle cacheis the preferred version andbundle packageremains as an alias #7389 - Display some basic
bundlerdocumentation together with ruby's RDoc based documentation #7394
Bugfixes:
- Fix typos deprecation message and upgrading docs #7374
- Deprecation warnings about
taintusage on ruby 2.7 #7385 - Fix
--helpflag not correctly delegating tomanwhen used with command aliases #7388 bundle addshould 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/inlinewarning aboutBundler.rootredefinition #7417
2.1.0.pre.2 (September 15, 2019)
Bugfixes:
- Fix
bundle cleantrying to delete non-existent directory (#7340) - Fix warnings about keywork 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 comunicate 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s #6728
- Make
bundle cleanalso clean native extensions for gems with a git source #7058 - Fix
bundle info bundlerto show the correct path to the bundler gem #7026 - Fix
bundle config build.<gem>not sending multiple parameters toextconf.rbcorrectly #7023 - Fix bad error message on Gemfile errors under ruby 2.7 (still unreleased, but it's a bugfix for beta testers after all) #7038
- Warn about situations where multiple gems provide the same executable (#7075)
- Ignore
frozensetting in inline mode (#7125) - Fix incorrect "bundler attempted to update GEM but version stayed the same" message when updating git sourced gems (#6325)
- Don't check for existance of a writable home directory if
BUNDLE_USER_HOMEis set (#6885) - Fix error message when server would respond to a bad username/password requiest with a 401 (#6928)
- Fix
bundle outdatedpluralization when multiple groups are requested (#7063) - Fix
bundle installnot updating conservatively when gemspec is changed (#7143) - Fix
bundle execnot respecting custom process titles inside scripts (#7140) - Fix
bundle updatemessage about exclude groups saying "installed" instead of "updated" (#7150) - Fix
bundle licensesnot showing correct information about bundler itself (#7147) - Fix installation path not including ruby scope when
BUNDLE_PATHwas set (#7163) - Fix
bundle cleanincorrectly removing git depedencies present in the Gemfile when rubygems 3.0+ was used and path involved a symlink (#7211) - Fix platform specific gems always being re-resolved when bundler was not running under that platform (#7212)
- Fix
bundle package --all-platformscausingbundle installto ignore--withand--without(#6113) - Fix
MissingRevisiongit errors to include the specificgitcommand that failed under the hood (#7225) - Fix using gemspec &
force_ruby_platformon Windows (#6809) - Make bundler's bins...
v2.1.0.pre.2
Bugfixes:
- Fix
bundle cleantrying to delete non-existent directory (#7340) - Fix warnings about keywork 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 comunicate 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s #6728
- Make
bundle cleanalso clean native extensions for gems with a git source #7058 - Fix
bundle info bundlerto show the correct path to the bundler gem #7026 - Fix
bundle config build.<gem>not sending multiple parameters toextconf.rbcorrectly #7023 - Fix bad error message on Gemfile errors under ruby 2.7 (still unreleased, but it's a bugfix for beta testers after all) #7038
- Warn about situations where multiple gems provide the same executable (#7075)
- Ignore
frozensetting in inline mode (#7125) - Fix incorrect "bundler attempted to update GEM but version stayed the same" message when updating git sourced gems (#6325)
- Don't check for existance of a writable home directory if
BUNDLE_USER_HOMEis set (#6885) - Fix error message when server would respond to a bad username/password requiest with a 401 (#6928)
- Fix
bundle outdatedpluralization when multiple groups are requested (#7063) - Fix
bundle installnot updating conservatively when gemspec is changed (#7143) - Fix
bundle execnot respecting custom process titles inside scripts (#7140) - Fix
bundle updatemessage about exclude groups saying "installed" instead of "updated" (#7150) - Fix
bundle licensesnot showing correct information about bundler itself (#7147) - Fix installation path not including ruby scope when
BUNDLE_PATHwas set (#7163) - Fix
bundle cleanincorrectly removing git depedencies present in the Gemfile when rubygems 3.0+ was used and path involved a symlink (#7211) - Fix platform specific gems always being re-resolved when bundler was not running under that platform (#7212)
- Fix
bundle package --all-platformscausingbundle installto ignore--withand--without(#6113) - Fix
MissingRevisiongit errors to include the specificgitcommand that failed under the hood (#7225) - Fix using gemspec &
force_ruby_platformon Windows (#6809) - Make bundler's binstub checks on bundler version consistent with rubygems
BundlerVersionFinder(#7259) - Fix
bundle installandbundle updategenerating different lockfiles whenpath:gems with relative paths starting with "./" were used (#7264) - Give a proper error when user tries to
bundle opena default gem (#7288) - Fix
bundle doctorcommand (#7309) - Fix bundler giving an unclear recommendation when duplicated gems are found in the Gemfile (#7302)
Documentation:
- Fix typo on a file extension in
bundle.ronn#7146 - Fix incorrect default value for
cache_pathconfiguration (#7229) - Binstubs documentation has been improved (#5889)
- Fix incorrect sections when explaining
:git,:branch, and:refoptions (#7265) - Fix mentions to remembered options in docs to explain the current state (#7242)
Internally, there's also...
v2.1.0.pre.1
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 comunicate 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
configcommand using subcommands (#5981) - Add
bundle plugin listcommand (#6120) - Introduce a
bundle lock --gemfileflag (#6748) - Add local git repository source option (
--local_git) to plugin installation (#6749) - Add
quietflag to inline bundler (#6828) - Introduce a
prefer_patchconfiguration that makesbundle updatebehave likebundle update --patch(#6931) - Introduce
Bundler.original_systemandBundler.original_execto shell out or exec to external programs using the original environment before bundler was loaded (#7052) - Add feature parity to
bundle info GEMwith respect to the old deprecated commandbundle show GEM#7026 - Introduce
bundle listto list groups of gems in your Gemfile. This command was actually documented, but was working as an alias tobundle showso this could also be considered a bug fix :) #7072 - Introduce
bundle outdated --filter-strictas an alias tobundle outdated --strict#6030 - Add
:gitand:branchoptions tobundle add(#7127) - Add
:ruby_26as a valid value to the:platform(s)dsl (#7155) - Let the
bundle cachecommand include all features currently provided bybundle package(#7249) - Several improvements on new gem templates (#6924, #6968, #7209, #7222, #7238)
- Add
--[no-]gitoption tobundle gemto generate non source control gems. Useful for monorepos, for example (#7263)
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
.gemfile 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 NAMEwhen 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)
- Include the exact bundler version in the lock file in the suggested command when bundler warns about version mismatches of itself #6971
- Fix plugins being installed every time a command is run ##6978
- Fallback to sequentially fetching specs on 429s #6728
- Make
bundle cleanalso clean native extensions for gems with a git source #7058 - Fix
bundle info bundlerto show the correct path to the bundler gem #7026 - Fix
bundle config build.<gem>not sending multiple parameters toextconf.rbcorrectly #7023 - Fix bad error message on Gemfile errors under ruby 2.7 (still unreleased, but it's a bugfix for beta testers after all) #7038
- Warn about situations where multiple gems provide the same executable (#7075)
- Ignore
frozensetting in inline mode (#7125) - Fix incorrect "bundler attempted to update GEM but version stayed the same" message when updating git sourced gems (#6325)
- Don't check for existance of a writable home directory if
BUNDLE_USER_HOMEis set (#6885) - Fix error message when server would respond to a bad username/password requiest with a 401 (#6928)
- Fix
bundle outdatedpluralization when multiple groups are requested (#7063) - Fix
bundle installnot updating conservatively when gemspec is changed (#7143) - Fix
bundle execnot respecting custom process titles inside scripts (#7140) - Fix
bundle updatemessage about exclude groups saying "installed" instead of "updated" (#7150) - Fix
bundle licensesnot showing correct information about bundler itself (#7147) - Fix installation path not including ruby scope when
BUNDLE_PATHwas set (#7163) - Fix
bundle cleanincorrectly removing git depedencies present in the Gemfile when rubygems 3.0+ was used and path involved a symlink (#7211) - Fix platform specific gems always being re-resolved when bundler was not running under that platform (#7212)
- Fix
bundle package --all-platformscausingbundle installto ignore--withand--without(#6113) - Fix
MissingRevisiongit errors to include the specificgitcommand that failed under the hood (#7225) - Fix using gemspec &
force_ruby_platformon Windows (#6809) - Make bundler's binstub checks on bundler version consistent with rubygems
BundlerVersionFinder(#7259) - Fix
bundle installandbundle updategenerating different lockfiles whenpath:gems with relative paths starting with "./" were used (#7264) - Give a proper error when user tries to
bundle opena default gem (#7288) - Fix
bundle doctorcommand (#7309) - Fix bundler giving an unclear recommendation when duplicated gems are found in the Gemfile (#7302)
Documentation:
- Fix typo on a file extension in
bundle.ronn#7146 - Fix incorrect default value for
cache_pathconfiguration (#7229) - Binstubs documentation has been improved (#5889)
- Fix incorrect sections when explaining
:git,:branch, and:refoptions (#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.
v2.0.2
Changes:
- Fixes for Bundler integration with ruby-src (#6941, #6973, #6977, #6315, #7061)
- Use
__dir__instead of__FILE__when generating a gem withbundle gem(#6503) - Use
httpson externals links in the Bundler gemspec (#6721) - Removed duplicate gem names from the suggested
did you meanlist for gem typos (#6739) - Removed Ruby 1.x compatibility code (#6764, #6806)
- Fixed an issue where
bundle removewould crash with certain Gemfiles (#6768) - Fixed indentation in the Bundler executable template (#6773)
- Fixed an issue where plugins could register for the same Bundler hook multiple times (#6775)
- Changed the "multiple sources" message in
bundle installto be a warning instead of an error (#6790) - Fixed a bug where path gems would break when using
only_update_to_newer_versions(#6774) - Fixed a bug where installing plugins with the
--delpoymentsetting would fail (#6805) - Fixed an issue where
bundle updatecouldn't update & install a gem whenno_installwas set (abundle packageconfig) (#7078) - Fixed an issue where users could not run
bundle execon default gems (#6963) - Updated vendor libraries to their latest version (#7076, #7068)
- Fixed an issue where the
githubsource was not usinghttpsby default that we mentioned in the 2.0 release (#7182) - Fixed an issue where
rake releasewas not outputting the message to users asking for a 2fa token (#7199)
Documentation: