Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/actions/runs/703745101?check_suite_focus=true#step:16:27
```
An error occurred in a `before(:suite)` hook.
Failure/Error: contents = File.read(version_file)
Errno::ENOENT:
No such file or directory @ rb_sysopen - /home/runner/work/actions/actions/snapshot-master/tmp/1/bundler-2.2.0.dev/lib/bundler/version.rb
```
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3114
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3114
|
|
Fix up previous commit
ref
9aa75795f9f438d5c874d8e418c3c7cdd63024fa,
38002a8adbd98266426940d829429a30af0622a4, and
0e60b59d5884edb8f9aea023efd9b24f1ff02049
|
|
ref 9aa75795f9f438d5c874d8e418c3c7cdd63024fa
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3105
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3086
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3086
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3086
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2822
|
|
https://github.com/bundler/bundler/commit/29d932d72d
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2753
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2753
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2683
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2683
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2674
|
|
Features:
- Add caller information to some deprecation messages to make them easier to fix [#7361](https://github.com/bundler/bundler/pull/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](https://github.com/bundler/bundler/pull/7389)
- Display some basic `bundler` documentation together with ruby's RDoc based documentation [#7394](https://github.com/bundler/bundler/pull/7394)
Bugfixes:
- Fix typos deprecation message and upgrading docs [#7374](https://github.com/bundler/bundler/pull/7374)
- Deprecation warnings about `taint` usage on ruby 2.7 [#7385](https://github.com/bundler/bundler/pull/7385)
- Fix `--help` flag not correctly delegating to `man` when used with command aliases [#7388](https://github.com/bundler/bundler/pull/7388)
- `bundle add` should cache newly added gems if an application cache exists [#7393](https://github.com/bundler/bundler/pull/7393)
- Stop using an insecure folder as a "fallback home" when user home is not defined [#7416](https://github.com/bundler/bundler/pull/7416)
- Fix `bundler/inline` warning about `Bundler.root` redefinition [#7417](https://github.com/bundler/bundler/pull/7417)
Notes:
Merged: https://github.com/ruby/ruby/pull/2668
|
|
|
|
https://github.com/bundler/bundler/commit/a38161c5be
|
|
https://github.com/bundler/bundler/commit/faccc522d1
|
|
https://github.com/bundler/bundler/commit/23007cb107
|
|
https://github.com/bundler/bundler/commit/52b6b94068
|
|
|
|
* These seem to consistenly pass already
* Show actual command when running `make test-bundler`
Current the setup command that installs the necessary gems for testing
bundler was printed, but not the actual command that runs the tests.
That was a bit confusing.
* Borrow trick from setproctitle specs
* A title that long doesn't get set sometimes
No idea why, but the test doesn't need that the title is that long.
* Fix most gem helper spec ruby-core failures
* Fix the rest of the gem helper failures
* Fix version spec by improving the assertion
* Remove unnecessary `BUNDLE_RUBY` environment var
We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name
because bundler considers `BUNDLE_*` variables as settings.
* Rename `BUNDLE_GEM` to `GEM_COMMAND`
This is more descriptive I think, and also friendlier for bundler
because `BUNDLE_` env variables are interpreted by bundler as settings,
and this is not a bundler setting.
This fixes one bundler spec failure in config specs against ruby-core.
* Fix quality spec when run in core
Use the proper path helper.
* Fix dummy lib builder to never load default gems
If a dummy library is named as a default gem, when requiring the library
from its executable, the default gem would be loaded when running from
core, because in core all default gems share path with bundler, and thus
they are always in the $LOAD_PATH. We fix the issue by loading lib
relatively inside dummy lib executables.
* More exact assertions
Sometimes I have the problem that I do some "print debugging" inside
specs, and suddently the spec passes. This happens when the assertion is
too relaxed, and the things I print make it match, specially when they
are simple strings like "1.0" than can be easily be part of gem paths
that I print for debugging.
I fix this by making a more exact assertion.
* Detect the correct shebang when ENV["RUBY"] is set
* Relax assertion
So that the spec passes even if another paths containing "ext" are in
the load path. This works to fix a ruby-core issue, but it's a better
assertion in general. We just want to know that the extension path was
added.
* Use folder structure independent path helper
It should fix this spec for ruby-core.
* Fix the last failing spec on ruby-core
* Skip `bundle open <default_gem>` spec when no default gems
|
|
The version we're vendoring actually relaxed this restriction back to
2.3.0+, so we can always use the vendored version.
https://github.com/bundler/bundler/commit/d366cbfe5d
|
|
Instead, make sure we always load the local copy of bundler during
specs, and never end up using the default copy.
https://github.com/bundler/bundler/commit/ac655ffeda
|
|
https://github.com/bundler/bundler/commit/f9cb39e614
|
|
https://github.com/bundler/bundler/commit/71a29e286a
|
|
https://github.com/bundler/bundler/commit/948a863bd8
|
|
https://github.com/bundler/bundler/commit/a4beba4cbf
|
|
https://github.com/bundler/bundler/commit/f20c2bdf6a
|
|
They are implicit inside `gem_command!`.
https://github.com/bundler/bundler/commit/6bdb13c899
|
|
https://github.com/bundler/bundler/commit/a4cca66b79
|
|
https://github.com/bundler/bundler/commit/7888d621c8
|
|
Since I plan to reuse it for something else.
https://github.com/bundler/bundler/commit/5379382198
|
|
https://github.com/bundler/bundler/commit/096e53dfe6
|
|
https://github.com/bundler/bundler/commit/028dc46f5a
|
|
https://github.com/bundler/bundler/commit/d35e31d2e0
|
|
The logic for choosing `gem_bin` should work here too even if it's not
identical.
https://github.com/bundler/bundler/commit/6ca0271b27
|
|
For debuggability.
https://github.com/bundler/bundler/commit/ac3e8db658
|
|
https://github.com/bundler/bundler/commit/8eedbecac0
|
|
https://github.com/bundler/bundler/commit/17d4d0de8e
|
|
https://github.com/bundler/bundler/commit/cae948f514
|
|
https://github.com/bundler/bundler/commit/039604ff95
|
|
https://github.com/bundler/bundler/commit/f2df73bdb4
|
|
https://github.com/bundler/bundler/commit/4589a57852
|
|
https://github.com/bundler/bundler/commit/afdacd62ac
|
|
This has the benefit that:
* Allows the installation of bundler as a default gem from rubygems to
include man pages.
* Removes the need to build man pages during our tests.
* Makes working with the manifest easier, because we only have source
controlled files, and not a mix of source control and generated files.
To make sure they never fall out of sync, we replace the previous
`man:build` CI task with a `man:check` task that makes sure the
generated man pages are up to date.
https://github.com/bundler/bundler/commit/23de1d0177
Notes:
Merged: https://github.com/ruby/ruby/pull/2366
|
|
Because we're using `config.bisect_runner` which is only available from
3.8.
https://github.com/bundler/bundler/commit/304a187f72
Notes:
Merged: https://github.com/ruby/ruby/pull/2366
|
|
failing tests for ruby < 2.6"
This reverts commit e63e844bc7444c6a489fcde0dc7011c6c4807edd.
It was introduced to resolve some failing tests at the cost of making
the intention of the spec much less clear.
Thanks to the previous fixes we have added to this spec, we can revert
that patch now.
https://github.com/bundler/bundler/commit/b29a40820f
Notes:
Merged: https://github.com/ruby/ruby/pull/2366
|