ruby.git/lib/bundler/installer, branch v3_3_11

Merge RubyGems-3.5.19 and Bundler-2.5.19

2024-09-25T17:56:17+00:00

Update RubyGems 3.5.16 and Bundler 2.5.16 for Ruby 3.3 (#11252)

2024-07-30T16:05:54+00:00

* Merge RubyGems-3.5.12 and Bundler-2.5.12

* Merge RubyGems-3.5.13 and Bundler-2.5.13

* Merge RubyGems-3.5.14 and Bundler-2.5.14

* Merge RubyGems-3.5.15 and Bundler-2.5.15

* Merge RubyGems-3.5.16 and Bundler-2.5.16

[rubygems/rubygems] Allow bundle pristine to run in parallel

2023-12-12T02:10:53+00:00

Also fix running when BUNDLE_NO_INSTALL happens to be set, same as with install/update commands

https://github.com/rubygems/rubygems/commit/a555fd6ccd

[rubygems/rubygems] Use modern hashes consistently

2023-12-07T22:29:33+00:00

https://github.com/rubygems/rubygems/commit/bb66253f2c

[rubygems/rubygems] Reduce allocations when installing gems with bundler

2023-11-26T22:07:39+00:00

```
==> memprof.after.txt <==
Total allocated: 1.13 MB (2352 objects)
Total retained:  10.08 kB (78 objects)

==> memprof.before.txt <==
Total allocated: 46.27 MB (38439 objects)
Total retained:  9.94 kB (75 objects)
```

Yes, we were allocating 45MB of arrays in `dependencies_installed?`,
it was accidentally cubic.

https://github.com/rubygems/rubygems/commit/13ab874388

[rubygems/rubygems] Better error when having an insecure install folder

2023-11-08T00:04:28+00:00

https://github.com/rubygems/rubygems/commit/e41156e272

[rubygems/rubygems] Remove redundant error class

2023-11-08T00:04:28+00:00

It's a `BundlerError`.

https://github.com/rubygems/rubygems/commit/53ea676dab

Re-resolve when lockfile is invalid

2023-10-16T04:49:49+00:00

Move the check for unmet dependencies in lockfile just in time to be
able to re-resolve if unmet dependencies are found.

[rubygems/rubygems] Prevent gem activation in standalone mode

2023-10-03T17:16:19+00:00

As discussed in https://github.com/rubygems/rubygems/issues/6273#issuecomment-1449176658

The `gem` method behaves awkwardly in standalone mode. Assuming bundler
isn't loaded at all, a call to gem might activate a gem that is not part
of the bundle (because it's the gem method defined in
lib/rubygems/core_ext/kernel_gem.rb and not
lib/bundler/rubygems_integration.rb). And when running with
`--disable-gems`, the gem method won't be defined at all so we'll get a
NoMethodError.

Calls to `gem` can appear in dependencies outside an application's
control. To work around this at GitHub we defined our own `Kernel#gem`
that no-ops.

I agree with https://github.com/rubygems/rubygems/issues/6273#issuecomment-1440755882

> people using standalone mode don't want to activate gems like Kernel.gem

This commit redefines `Kernel#gem` in the standalone script to no-op.

https://github.com/rubygems/rubygems/commit/bea17b55f1

[rubygems/rubygems] Centralize logic using `Pathname#relative_path_from`

2023-09-27T05:20:58+00:00

To avoid potential crashes when trying to jump from a drive to another
on Windows, and take the change refactor things a bit.

https://github.com/rubygems/rubygems/commit/7c9a9a431a