ruby.git/test/rubygems/test_gem_commands_setup_command.rb, branch v4.0.4 The Ruby Programming Language [ruby/rubygems] Extract and generate only bundler bin files instead of full installation. 2025-12-08T23:52:15+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2025-12-08T06:33:54+00:00 ca8630b6363a706a43bfdb5a3359addcfb616d19 https://github.com/ruby/rubygems/commit/a70e573973 
https://github.com/ruby/rubygems/commit/a70e573973
[rubygems/rubygems] Allow enabling "Bundler 3 mode" more easily 2025-06-19T01:23:36+00:00 David Rodríguez deivid.rodriguez@riseup.net 2023-03-13T13:28:27+00:00 4245d522b2af5c17a08b3555ffed011a5aa508b2 Currently to test Bundler 3 mode we have to actually edit the version file to simulate we're running a future version. This is inconvenient. Instead, allow passing an environment variable, `BUNDLER_3_MODE`, to set the "working mode" Bundler should use. This can now be set easily by end users to enable them to try out the changes in the future version and give us feedback. It's unclear how version auto-switching should work when this environment variable is set, so the auto-switching feature will be disabled in that case. https://github.com/rubygems/rubygems/commit/4e92e9b209 
Currently to test Bundler 3 mode we have to actually edit the version
file to simulate we're running a future version. This is inconvenient.

Instead, allow passing an environment variable, `BUNDLER_3_MODE`, to set
the "working mode" Bundler should use.

This can now be set easily by end users to enable them to try out the
changes in the future version and give us feedback.

It's unclear how version auto-switching should work when this
environment variable is set, so the auto-switching feature will be
disabled in that case.

https://github.com/rubygems/rubygems/commit/4e92e9b209
[rubygems/rubygems] Fix headings levels in Changelogs 2025-06-05T10:12:39+00:00 Antoine Marguerie antoine@basesecrete.com 2025-05-21T13:07:54+00:00 11492bd88d98edeaac4d3e35dd0d59bf67a79569 And adapt release scripts and configuration to the new structure. https://github.com/rubygems/rubygems/commit/3deb1aedae 
And adapt release scripts and configuration to the new structure.

https://github.com/rubygems/rubygems/commit/3deb1aedae
[rubygems/rubygems] Fix `gem update --system` leaving old default bundler executables around 2024-10-30T14:22:08+00:00 David Rodríguez deivid.rodriguez@riseup.net 2024-10-21T11:43:36+00:00 1e1a37220b18873cd227da2e9b788a62c41707df https://github.com/rubygems/rubygems/commit/4b81add54c 
https://github.com/rubygems/rubygems/commit/4b81add54c
[rubygems/rubygems] Fix binstubs sometimes not getting regenerated when `--destdir` is given 2024-05-16T13:34:33+00:00 David Rodriguez deivid.rodriguez@riseup.net 2024-05-09T15:51:44+00:00 c55c11d7d5813683dde3eb7791bc2a9d5d39556d This was only working for gems also installed in the default gem home. https://github.com/rubygems/rubygems/commit/47df02dbd9 
This was only working for gems also installed in the default gem home.

https://github.com/rubygems/rubygems/commit/47df02dbd9
[rubygems/rubygems] Remove `travis_removal_info` 2024-01-29T05:39:13+00:00 Masato Ohba over.rye@gmail.com 2024-01-27T13:35:38+00:00 933ede5d768a0e411336ea27840727442c42d3df `travis_removal_info` is added by https://github.com/rubygems/rubygems/pull/6150. According to the comment, it's supposed to be removed at bundler v2.5.0 but it hasn't. https://github.com/rubygems/rubygems/commit/e18797d43f 
`travis_removal_info` is added by https://github.com/rubygems/rubygems/pull/6150. According to the comment, it's supposed to be removed at bundler v2.5.0 but it hasn't.

https://github.com/rubygems/rubygems/commit/e18797d43f
Merge RubyGems/Bundler master from 4076391fce5847689bf2ec402b17133fe4e32285 2023-05-30T12:50:07+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2023-05-30T11:25:29+00:00 4bbeed61346d6016e2d72818e8068bedcb9f006d 






[rubygems/rubygems] Load plugin immediately
2023-05-25T21:51:15+00:00

Sutou Kouhei
kou@clear-code.com

2022-09-13T00:57:42+00:00

d83f32c34b1d0e4dd49dd1f0af1b665c022b2872

We can install RubyGems plugin by "gem install XXX". The installed
plugin is used from the NEXT "gem ...".

For example, "gem install gem-src kaminari" doesn't use gem-src plugin
for kaminari. "gem install gem-src && gem install kaminari" uses
gem-src plugin for kaminari.

How about loading a plugin immediately when the plugin is installed?
If this proposal is implemented, "gem install gem-src kaminari" works
like "gem install gem-src && gem install kaminari".

https://github.com/rubygems/rubygems/commit/4917d96f4c





We can install RubyGems plugin by "gem install XXX". The installed
plugin is used from the NEXT "gem ...".

For example, "gem install gem-src kaminari" doesn't use gem-src plugin
for kaminari. "gem install gem-src && gem install kaminari" uses
gem-src plugin for kaminari.

How about loading a plugin immediately when the plugin is installed?
If this proposal is implemented, "gem install gem-src kaminari" works
like "gem install gem-src && gem install kaminari".

https://github.com/rubygems/rubygems/commit/4917d96f4c







[rubygems/rubygems] util/rubocop -A --only Style/FormatString
2023-04-07T05:13:05+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2023-04-07T00:15:17+00:00

250e97c0fba48d1f87ccecb1b1e1b4bd2a30c388

https://github.com/rubygems/rubygems/commit/132a56569d





https://github.com/rubygems/rubygems/commit/132a56569d







[rubygems/rubygems] Use TestCase#util_spec instead of custom code.
2023-04-06T04:07:16+00:00

Vít Ondruch
vondruch@redhat.com

2019-09-11T13:39:55+00:00

b5f243291742886a1280277c2ff954177b4f50a7

https://github.com/rubygems/rubygems/commit/74d485ff1e





https://github.com/rubygems/rubygems/commit/74d485ff1e