ruby.git/lib/rubygems/core_ext, branch v4.0.3 The Ruby Programming Language [rubygems/rubygems] Avoid more warnings when using RubyGems with old Bundler 2025-07-14T02:52:14+00:00 David Rodríguez deivid.rodriguez@riseup.net 2025-07-10T17:46:39+00:00 c3d41492e14929f8bbee26a276ee76b9a8c9d5b6 We were only avoiding them when the RUBYGEMS_GEMDEPS variable is used. Avoid the warnings in general, whenever the entrypoint to Bundler is `require`. https://github.com/rubygems/rubygems/commit/8683faef36 
We were only avoiding them when the RUBYGEMS_GEMDEPS variable is used.
Avoid the warnings in general, whenever the entrypoint to Bundler is
`require`.

https://github.com/rubygems/rubygems/commit/8683faef36
[rubygems/rubygems] Update required_ruby_version to 3.1 2024-10-04T20:01:51+00:00 Samuel Giddins segiddins@segiddins.me 2024-10-02T01:20:19+00:00 bdc3363d0f045b1a6d81b72c3cd9b10d5759f71e 3.0 has been EOL since march, drop support for it before the 3.4 release is cut Signed-off-by: Samuel Giddins <segiddins@segiddins.me> https://github.com/rubygems/rubygems/commit/fc1f03b06a 
3.0 has been EOL since march, drop support for it before the 3.4 release is cut

Signed-off-by: Samuel Giddins <segiddins@segiddins.me>

https://github.com/rubygems/rubygems/commit/fc1f03b06a
Reapply "[rubygems/rubygems] Fix activation conflicts when circularly requiring a gem" 2024-01-22T00:57:10+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2024-01-19T04:32:53+00:00 00dc1cace803fa557c685e7cb395bfaa77bc03a9 This reverts commit 04cf66765a8a9d48baea6d9aee266dc9aa21df27. 
This reverts commit 04cf66765a8a9d48baea6d9aee266dc9aa21df27.
Reapply "[rubygems/rubygems] Fix `require` of a default gem when unresolved gems depend on it" 2024-01-22T00:57:10+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2024-01-19T04:32:45+00:00 d51f4c9288a2195fbf6889fca8790587f71a1cd9 This reverts commit 54552b89e73fc616ba47c1c87d33625af99cbce9. 
This reverts commit 54552b89e73fc616ba47c1c87d33625af99cbce9.
Revert "[rubygems/rubygems] Fix `require` of a default gem when unresolved gems depend on it" 2024-01-19T03:12:33+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2024-01-19T03:12:33+00:00 54552b89e73fc616ba47c1c87d33625af99cbce9 This reverts commit f1f5f22d22a149f20e019728b1ab35593d29d81a. 
This reverts commit f1f5f22d22a149f20e019728b1ab35593d29d81a.
Revert "[rubygems/rubygems] Fix activation conflicts when circularly requiring a gem" 2024-01-19T02:54:17+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2024-01-19T02:53:45+00:00 04cf66765a8a9d48baea6d9aee266dc9aa21df27 This reverts commit db44088c2a92040879386aa5f268db4c858e4e5b. https://github.com/ruby/ruby/actions/runs/7578672002/job/20641640821 https://github.com/ruby/ruby/actions/runs/7578672002/job/20641641212 https://github.com/ruby/ruby/actions/runs/7578672002/job/20641642031 
This reverts commit db44088c2a92040879386aa5f268db4c858e4e5b.

  https://github.com/ruby/ruby/actions/runs/7578672002/job/20641640821
  https://github.com/ruby/ruby/actions/runs/7578672002/job/20641641212
  https://github.com/ruby/ruby/actions/runs/7578672002/job/20641642031
[rubygems/rubygems] Fix activation conflicts when circularly requiring a gem 2024-01-19T02:28:11+00:00 David Rodríguez deivid.rodriguez@riseup.net 2024-01-12T13:53:40+00:00 db44088c2a92040879386aa5f268db4c858e4e5b If a gem is required circular, and there are unresolved specs depending on it, we may end up in an activation conflict. The solution is to not try to activate unresolved gems when requiring a default gem, regardless of it having already been activated or not. https://github.com/rubygems/rubygems/commit/3b2b8f4e3e 
If a gem is required circular, and there are unresolved specs depending
on it, we may end up in an activation conflict.

The solution is to not try to activate unresolved gems when requiring a
default gem, regardless of it having already been activated or not.

https://github.com/rubygems/rubygems/commit/3b2b8f4e3e
[rubygems/rubygems] Fix `require` of a default gem when unresolved gems depend on it 2024-01-19T02:28:11+00:00 David Rodríguez deivid.rodriguez@riseup.net 2024-01-11T20:53:26+00:00 f1f5f22d22a149f20e019728b1ab35593d29d81a The following conditions must be met: * A default gem is required. * A previous require left some gems unresolved, and those dependencies themselves depend on the default gem. In this case, rubygems require will first activate the default version of the gem, then try to activate another unresolved version of the default gem that conflicts with the first activation. The solution is, if we are in the middle of requiring a default gem, skip this step, because we have already activated it successfully. https://github.com/rubygems/rubygems/commit/8cd5608db5 Co-authored-by: Stan Hu <stanhu@gmail.com> 
The following conditions must be met:

* A default gem is required.
* A previous require left some gems unresolved, and those dependencies
  themselves depend on the default gem.

In this case, rubygems require will first activate the default version
of the gem, then try to activate another unresolved version of the
default gem that conflicts with the first activation.

The solution is, if we are in the middle of requiring a default gem,
skip this step, because we have already activated it successfully.

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

Co-authored-by: Stan Hu <stanhu@gmail.com>
[rubygems/rubygems] Add a comment to explain default gem activation 2024-01-19T02:28:10+00:00 David Rodríguez deivid.rodriguez@riseup.net 2024-01-11T22:02:11+00:00 8044e57907bc5a066ca9ef309d90c62906f8e2ec https://github.com/rubygems/rubygems/commit/291128268f 
https://github.com/rubygems/rubygems/commit/291128268f
[rubygems/rubygems] Remove now unnecessary dups 2023-11-13T02:06:10+00:00 David Rodríguez deivid.rodriguez@riseup.net 2023-10-27T18:50:20+00:00 3757d9027c612c88fdbf449eacf7f8f6c9b2e932 https://github.com/rubygems/rubygems/commit/56ce2a6445 
https://github.com/rubygems/rubygems/commit/56ce2a6445