This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
v1.14.0.pre.1
Pre-release
Pre-release
segiddins
released this
28 Aug 03:17
·
3890 commits
to master
since this release
Features:
bundle doctor
first runsbundle check
(@segiddins)- the bundler trampoline is automatically enabled when the target version is greater than bundler 2 (@segiddins)
- gem checksums returned by rubygems.org are validated when installing gems (#4464, @segiddins)
- use the git username as a github username when running
bundle gem
(@JuanitoFatas) - show more context when the resolver conflicts on required ruby and rubygems versions (@segiddins)
- improve platform support by allowing bundler to pick the best platform match during dependency resolution, enabled with the
specific_platform
setting (#4295, #4896, @segiddins) - always prompt the user for a password when using
sudo
(#3006, @segiddins) - support running without a home directory (#4778, @segiddins)
- print a warning when the gemfile uses a platform conditional that will exclude the gem from all lockfile platforms (@segiddins)
- add the
force_ruby_platform
setting to force bundler to install ruby-platform gems, even on other platforms (#4813, @segiddins) - add conservative update options to
bundle lock
(#4912, @chrismo) - improve
bundle outdated
output to group gems by group (@ryanfox1985) - add conservative update options to
bundle update
(#5065, #5076, @chrismo) - print the output of
bundle env
as github-flavored markdown, making it easier to preserve formatting when copy-pasting into a new issue (@segiddins) - configure the persistence file when using
bundle gem
withrspec
(@segiddins) - add support for the
ruby_25
gemfile filter (@amatsuda) - when installing with a lockfile that is missing dependencies, allow installation to proceed (but without parallelism) (@segiddins)
Performance:
- improve
require "bundler"
performance by ~5x (@segiddins) - allow install gems in parallel when running on rubygems 2+
Bugfixes:
- config files with CRLF line endings can be read (#4435, @segiddins)
bundle lock
activates gems for the current platform even if they were activated under a different platform for a separate dependency (#4896, @segiddins)- running
bundle env
in a directory without a gemfile no longer crashes (@segiddins) - fail gracefully when attempting to use a source with an unknown URI scheme (#4953, @segiddins)
- store paths in the lockfile relative to the root gemfile directory when using
eval_gemfile
(#4966, @segiddins) bundle lock
will not update without the--update
flag (#4957, @segiddins)- the
console
binstub generated bybundle gem
will load.irbrc
files (@mattbrictson) - print friendly filesystem access errors in the new index (@segiddins)
- print a helpful error when running out of memory on jruby (#4673, @segiddins)
- load all rubygems plugins when installing gems (#2824, @segiddins)
bundle clean --dry-run
prints the list of gems without the--force
option when no path is set (#5027, @hmistry)- local installs no longer print "this gem may have been yanked" (#5022, @hmistry)
- avoid leaking
which
output when runningbundle doctor
(@colby-swandale) - print a warning when attempting to
bundle exec
an empty program (#5084, @bronzdoc) - ensure
bundle outdated
lists all outdated gems (#4979, @chrismo) - fail gracefully when attempting to
bundle gem
with an invalid constant name (#5185, @segiddins) - allow
bundler/inline
to work in a directory that contains a gemfile (#5117, @colby-swandale) - ensure that the new index is thread-safe, allowing installation on rbx (#5142, @segiddins)
- remove deprecated
rspec
syntax inbundle gem
output (@gearnode)- fail gracefully when any system error is encountered when touching the filesystem (#5134, @segiddins)
- fix compatibility with a machine running with FIPS mode enabled (#4989, @segiddins)
- fix
bundle lock --add-platform ruby
(#5230, @segiddins) - print gem post-install messages when running
bundle update
(@smathy) - ensure errors due to a retries are all separated by a newline (@segiddins)
- print out the bundle path in gem not found errors (#4854, @diegosteiner)
- fail gracefully when creating threads fails (@segiddins)
- avoid downloading metadata for gems that are only development dependencies (@Paxa)