| Age | Commit message (Collapse) | Author |
|
Covers the four new hook events added in the previous commit:
before-fetch, after-fetch, before-git-fetch, after-git-fetch.
https://github.com/ruby/rubygems/commit/a08ea29297
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
https://github.com/ruby/rubygems/commit/fefe97c0bd
|
|
bundle_config/bundle_config_global
https://github.com/ruby/rubygems/commit/982ad09264
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
with in-process config helper
https://github.com/ruby/rubygems/commit/f5539440d5
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
This reverts commit d1b8503e59dc5171580efba9f33f256b79008bc4.
|
|
This simplifies running bundler tests from the repository root.
Tests can now be run with `bin/rspec spec/...` instead of needing
to chdir into bundler/ first.
https://github.com/ruby/rubygems/commit/28670c2e20
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
- ### Problem
When a plugin in the Gemfile is updated to a new version, it will
be downloaded but will not be registered. The old version of the
plugin will be loaded when Bundler is invoked.
### Context
The problem is in the `Index#installed?` method that only checks for
the plugin name in the index. If it finds one, it skips the
registration.
### Solution
Check whether the registed plugin load paths matche the new plugin
one. If not, register the new plugin which will override the
previous one in the index.
https://github.com/ruby/rubygems/commit/ac65001055
|
|
- ### Problem
Bundler crashes when a Gemfile contains a plugin and you
try to run `bundle install` while setting the BUNDLE_WITHOUT=default
value.
### Context
Setting the BUNDLE_WITHOUT=default is something that some deployment
tooling does like [shipit](https://github.com/Shopify/shipit-engine/blob/a24b9d8b1b777e22f05311705be7938a4823eee6/app/models/shipit/deploy_spec/bundler_discovery.rb#L6)
The intent being to only install gems that are required to deploy
the app (for instance ones that are inside a `group :deploy` block).
### Solution
Bundler assume that all plugins inside the Gemfile will get
installed, but don't take in consideration that a BUNDLE_WITHOUT
may have affected this.
So before registering a plugin, make sure it's actually in
the `specs` object (meaning it was installed on disk).
https://github.com/ruby/rubygems/commit/b416a026ca
|
|
https://github.com/ruby/rubygems/commit/602b0cecb8
Co-authored-by: hsbt <12301+hsbt@users.noreply.github.com>
|
|
https://github.com/ruby/rubygems/commit/b8d45956d0
|
|
This is a first pass to improve the way errors are handled and raised in
bundler's tests. The goal is to clean up tests and modernize them -
these were some obvious areas that could be cleaned up.
- Instead of raising "ZOMG" in the load error tests, it now tests for
the actual error and gem raising.
- Improve error messages where applicable.
- All errors raise a specific error class, rather than falling back to a
default and just setting a message.
- Removed arguments and `bundle_dir` option from `TheBundle` class as it wasn't
actually used so therefore we don't need to raise an error for extra
arguments.
- Removed error from `BundlerBuilder`, as it won't work if it's not
`bundler`, also it never uses `name`. The only reaon `name` is passed
in is because of metaprogramming on loading the right builder. I
think that should eventually be refactored.
- Replaced and removed `update_repo3` and `update_repo4` in favor of
just `build_repo3` and `build_repo4`. Rather than tell someone writing
tests to use a different method, automatically use the right method.
https://github.com/ruby/rubygems/commit/68c39c8451
|
|
https://github.com/ruby/rubygems/commit/d3baf4110e
|
|
And make it a standard setting.
https://github.com/rubygems/rubygems/commit/17e356fa94
|
|
an error
https://github.com/rubygems/rubygems/commit/8bfe317e6d
|
|
Since now every functionality that changes in Bundler 4 is under a
setting, we can enable that setting to test the new functionality,
without having to run our full CI twice.
This can actually be seen as increasing coverage, because Bundler 4
functionality will now be tested on Windows, MacOS, or any other
environment where previously "Bundler 4 mode" was not running.
https://github.com/rubygems/rubygems/commit/1cb3e009fc
|
|
https://github.com/rubygems/rubygems/commit/28b6a7cf5e
|
|
https://github.com/rubygems/rubygems/commit/e891be9197
Notes:
Merged: https://github.com/ruby/ruby/pull/12968
|
|
Because it does not swallow errors if it fails to remove the given
folders, making issues easier to debug.
https://github.com/rubygems/rubygems/commit/0db12d7afc
|
|
And get specs passing.
https://github.com/rubygems/rubygems/commit/c23b5f5b84
|
|
|
|
https://github.com/rubygems/rubygems/commit/4bcdb854a2
|
|
https://github.com/rubygems/rubygems/commit/e3d180620c
|
|
https://github.com/rubygems/rubygems/commit/b373b7ed0d
|
|
This affected both CLI and Gemfile installs
https://github.com/rubygems/rubygems/commit/a0d101a8df
|
|
Also bring the man page up to date.
https://github.com/rubygems/rubygems/commit/a849bd6947
|
|
Ensure only one source type is specified, and ensure options that
are only relevant to git sources are only specified with git.
https://github.com/rubygems/rubygems/commit/58b043215e
|
|
It's the exact same implementation as --git
https://github.com/rubygems/rubygems/commit/18eb2418c6
|
|
https://github.com/rubygems/rubygems/commit/bb66253f2c
|
|
Looks for the CHECKSUMS section in the lockfile, activating the feature
only if the section exists. Without a CHECKSUMS section, Bundler will
continue as normal, validating checksums when gems are installed while
checksums from the compact index are present.
https://github.com/rubygems/rubygems/commit/2353cc93a4
|
|
https://github.com/rubygems/rubygems/commit/8d51390ca4
|
|
We lock the checksum for each resolved spec under a new CHECKSUMS
section in the lockfile.
If the locked spec does not resolve for the local platform, we preserve
the locked checksum, similar to how we preserve specs.
Checksum locking only makes sense on install. The compact index
information is only available then.
https://github.com/rubygems/rubygems/commit/bde37ca6bf
|
|
Plugins don't use a lockfile, so ignore frozen related settings.
https://github.com/rubygems/rubygems/commit/f17a3bb81f
|
|
https://github.com/rubygems/rubygems/commit/16c3535413afebcdbab7582c6017c27b5da8a8dc
Notes:
Merged: https://github.com/ruby/ruby/pull/6326
|
|
https://github.com/rubygems/rubygems/commit/482077d185
|
|
It doesn't add anything.
https://github.com/rubygems/rubygems/commit/ece3c864df
|
|
versions
https://github.com/rubygems/rubygems/commit/9c88db949d
Notes:
Merged: https://github.com/ruby/ruby/pull/4789
|
|
The error had not be caught be specs because `bundle install` was
returning a zero exit code when plugin installation errors happened. So
I fixed that issue too.
https://github.com/rubygems/rubygems/commit/90cde87856
Notes:
Merged: https://github.com/ruby/ruby/pull/4789
|
|
This is in preparation for deprecating source-less gemfiles.
https://github.com/rubygems/rubygems/commit/d6493fa3e2
|
|
install`'s help
https://github.com/rubygems/rubygems/commit/b7b7d16aa8
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4648
|
|
55634a8af18a52df86c4275d70fa1179118bcc20
Notes:
Merged: https://github.com/ruby/ruby/pull/4021
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3864
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3659
|
|
https://github.com/rubygems/rubygems/commit/27e0e4ecb6
Notes:
Merged: https://github.com/ruby/ruby/pull/3275
|
|
https://github.com/rubygems/rubygems/commit/4d1a0c465a
Notes:
Merged: https://github.com/ruby/ruby/pull/3212
|
|
https://github.com/rubygems/rubygems/commit/746a4b3d74
Notes:
Merged: https://github.com/ruby/ruby/pull/3212
|
|
https://github.com/rubygems/rubygems/commit/ade0c441d5
Notes:
Merged: https://github.com/ruby/ruby/pull/3212
|
|
Instead, use the non-deprecated option except when specifically testing
deprecated CLI flags. In that case, pass the flag directly and limit
the specs to `bundler < 3`.
https://github.com/rubygems/rubygems/commit/3d5e186241
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/f878a81f22
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3114
|