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

Merge RubyGems-3.5.21 and Bundler-2.5.21

2024-10-17T15:55:01+00:00

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

Merge RubyGems 3.5.11 and Bundler 2.5.11 for Ruby 3.3 (#10870)

2024-06-05T04:36:46+00:00

Co-authored-by: Nobuyoshi Nakada

Merge RubyGems 3.5.9 and Bundler 2.5.9 (Fixed CI at Ruby 3.3) (#10348)

2024-04-16T02:22:22+00:00

* Merge RubyGems-3.5.6 and Bundler-2.5.6

* Merge RubyGems-3.5.7 and Bundler-2.5.7

* Merge RubyGems-3.5.8 and Bundler-2.5.8

* Partly reverted about https://github.com/rubygems/rubygems/pull/7483

* Merge RubyGems-3.5.9 and Bundler-2.5.9

[rubygems/rubygems] Use mkdir_p helper in bundler.rb

2023-12-15T15:32:56+00:00

Small refactor, no functional change

https://github.com/rubygems/rubygems/commit/5edb7a1026

[rubygems/rubygems] Remove doc not adding much value

2023-12-12T01:04:57+00:00

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

[rubygems/rubygems] Use modern hashes consistently

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

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

[rubygems/rubygems] Duplicate Gem::CIDetector into bundler

2023-12-06T20:05:25+00:00

Because bundler needs to support older versions of rubygems, we can't
actually rely on Gem::CIDetector (yet - in a year or so they might be
able to consolidate, if they don't change futher). So we're copying it
into the Bundler:: namespace, and enforcing that they stay completely in
sync with a test. No other tests are needed, since Gem::CIDetector is
already tested, and this is and will remain identical.

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

[rubygems/rubygems] Many major_deprecations supply :removed_message

2023-12-01T17:52:38+00:00

Generally the removed message is very similar, but often it needs to
specify that the feature has "been removed" instead of "will be
removed", or "been deprecated". And a few chunks of text needed more
substantial updates. And a number of them seemed to have been carefully
crafted to make sense in either context, so I left those alone.

https://github.com/rubygems/rubygems/commit/8d42cf9104