Unclaimed project
Are you a maintainer of bundler? Claim this project to take control of your public changelog and roadmap.
Changelog
Manage your Ruby application's gem dependencies
Bugfixes:
net-http-pipeline no longer being allowed in Gemfiles if already installed in the system due to our vendored version of net-http-persistent optionally requiring it #7529Bugfixes:
rake build when path has spaces on it #7514rake release git push tasks when the running shell has git as an alias of another command (like hub) #7510bundle config set deployment true recommended alternative to bundle config --deployment to behave in the same way as the --deployment flag #7519Bugfixes:
require "rubygems" on top rubygems_integration.rb to avoid some missing constant errors under some convoluted setups #7505Bugfixes:
Features:
Bugfixes:
Changes:
Features:
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 #7389bundler documentation together with ruby's RDoc based documentation #7394Bugfixes:
taint usage on ruby 2.7 #7385--help flag not correctly delegating to man when used with command aliases #7388bundle add should cache newly added gems if an application cache exists #7393bundler/inline warning about Bundler.root redefinition #7417Bugfixes:
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:
Features:
config command using subcommands (#5981)bundle plugin list command (#6120)bundle lock --gemfile flag (#6748)--local_git) to plugin installation (#6749)quiet flag to inline bundler (#6828)prefer_patch configuration that makes bundle update behave like bundle update --patch (#6931)Bundler.original_system and Bundler.original_exec to shell out or exec to external programs using the original environment before bundler was loaded (#7052)bundle info GEM with respect to the old deprecated command bundle show GEM #7026bundle list to list groups of gems in your Gemfile. This command was actually documented, but was working as an alias to bundle show so this could also be considered a bug fix :) #7072bundle outdated --filter-strict as an alias to bundle outdated --strict #6030:git and :branch options to bundle add (#7127):ruby_26 as a valid value to the :platform(s) dsl (#7155)bundle cache command include all features currently provided by bundle package (#7249)--[no-]git option to bundle gem to generate non source control gems. Useful for monorepos, for example (#7263)Bugfixes:
.gem file from the cache if it's corrupted (#6010)bundle install, so that the outcome is independent from the major version of bundler being run (#6068)bundle outdated --group NAME when the group is listed second in the Gemfile (#6116)required_ruby_version, and by filtering out requirements that didn't contribute to the conflict (#6647)bundle clean also clean native extensions for gems with a git source #7058bundle info bundler to show the correct path to the bundler gem #7026bundle config build.<gem> not sending multiple parameters to extconf.rb correctly #7023frozen setting in inline mode (#7125)BUNDLE_USER_HOME is set (#6885)bundle outdated pluralization when multiple groups are requested (#7063)bundle install not updating conservatively when gemspec is changed (#7143)bundle exec not respecting custom process titles inside scripts (#7140)bundle update message about exclude groups saying "installed" instead of "updated" (#7150)bundle licenses not showing correct information about bundler itself (#7147)BUNDLE_PATH was set (#7163)bundle clean incorrectly removing git depedencies present in the Gemfile when rubygems 3.0+ was used and path involved a symlink (#7211)bundle package --all-platforms causing bundle install to ignore --with and --without (#6113)MissingRevision git errors to include the specific git command that failed under the hood (#7225)force_ruby_platform on Windows (#6809)BundlerVersionFinder (#7259)bundle install and bundle update generating different lockfiles when path: gems with relative paths starting with "./" were used (#7264)bundle open a default gem (#7288)bundle doctor command (#7309)Documentation:
bundle.ronn #7146cache_path configuration (#7229):git, :branch, and :ref options (#7265)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.