<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ruby.git/lib/bundler/cli/install.rb, branch v4.0.2</title>
<subtitle>The Ruby Programming Language</subtitle>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/'/>
<entry>
<title>[ruby/rubygems] Tweak the Bundler's "X gems now installed message":</title>
<updated>2025-12-16T00:16:15+00:00</updated>
<author>
<name>Edouard CHIN</name>
<email>chin.edouard@gmail.com</email>
</author>
<published>2025-12-15T10:45:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=ff1b8ffa61922a46eae217c06aa16b24f26ae723'/>
<id>ff1b8ffa61922a46eae217c06aa16b24f26ae723</id>
<content type='text'>
- Fix https://github.com/ruby/rubygems/pull/9188
- This message is a bit misleading because it always outputs one extra
  specs, which is Bundler itself.

  This is now fixed when the message is about to be output.

https://github.com/ruby/rubygems/commit/70b4e19506
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- Fix https://github.com/ruby/rubygems/pull/9188
- This message is a bit misleading because it always outputs one extra
  specs, which is Bundler itself.

  This is now fixed when the message is about to be output.

https://github.com/ruby/rubygems/commit/70b4e19506
</pre>
</div>
</content>
</entry>
<entry>
<title>[ruby/rubygems] Support bundle install --lockfile option</title>
<updated>2025-11-25T08:09:52+00:00</updated>
<author>
<name>Jeremy Evans</name>
<email>code@jeremyevans.net</email>
</author>
<published>2025-11-23T04:31:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=e920ee32894dcd2ab0f97ff6f45c29d65024da0c'/>
<id>e920ee32894dcd2ab0f97ff6f45c29d65024da0c</id>
<content type='text'>
This allows for specifying the lockfile to read and write. It mirrors
the --gemfile option, and has higher priority than the lockfile
method in the Gemfile. It also mirrors the bundle lock --lockfile
option.

When the --lockfile option is used, it is applied twice. First, before
the Gemfile is read, to specify the lockfile to operate on, and again
after the Gemfile is read, so that if the Gemfile has a lockfile
method that overrides the defintion's lockfile, the --lockfile option
still has higher precedence.

https://github.com/ruby/rubygems/commit/17acdd4a89
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This allows for specifying the lockfile to read and write. It mirrors
the --gemfile option, and has higher priority than the lockfile
method in the Gemfile. It also mirrors the bundle lock --lockfile
option.

When the --lockfile option is used, it is applied twice. First, before
the Gemfile is read, to specify the lockfile to operate on, and again
after the Gemfile is read, so that if the Gemfile has a lockfile
method that overrides the defintion's lockfile, the --lockfile option
still has higher precedence.

https://github.com/ruby/rubygems/commit/17acdd4a89
</pre>
</div>
</content>
</entry>
<entry>
<title>[ruby/rubygems] Add support for bundle install --no-lock</title>
<updated>2025-11-20T23:01:03+00:00</updated>
<author>
<name>Jeremy Evans</name>
<email>code@jeremyevans.net</email>
</author>
<published>2025-11-09T00:03:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=1562803e5103dea3949027e61672fa82f26782fd'/>
<id>1562803e5103dea3949027e61672fa82f26782fd</id>
<content type='text'>
This allows for the same behavior as including `lockfile false`
in the Gemfile. This allows you to get the behavior without
modifying the Gemfile, which is useful if you do not control the
Gemfile.

This is similar to the --no-lock option already supported by
`gem install -g Gemfile`.

https://github.com/ruby/rubygems/commit/6c94623881

Co-authored-by: Colby Swandale &lt;996377+colby-swandale@users.noreply.github.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This allows for the same behavior as including `lockfile false`
in the Gemfile. This allows you to get the behavior without
modifying the Gemfile, which is useful if you do not control the
Gemfile.

This is similar to the --no-lock option already supported by
`gem install -g Gemfile`.

https://github.com/ruby/rubygems/commit/6c94623881

Co-authored-by: Colby Swandale &lt;996377+colby-swandale@users.noreply.github.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Replaced Bundler.feature_flag.plugins? to Bundler.settings</title>
<updated>2025-10-10T04:06:28+00:00</updated>
<author>
<name>Hiroshi SHIBATA</name>
<email>hsbt@ruby-lang.org</email>
</author>
<published>2025-10-10T02:30:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=282b0e3a8342de5fb5466f7b85ead83a9f5ac9f6'/>
<id>282b0e3a8342de5fb5466f7b85ead83a9f5ac9f6</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/ced8ef3a12

Co-authored-by: David Rodríguez &lt;2887858+deivid-rodriguez@users.noreply.github.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/ced8ef3a12

Co-authored-by: David Rodríguez &lt;2887858+deivid-rodriguez@users.noreply.github.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Move `bundle install --binstubs` deprecation to cli.rb</title>
<updated>2025-09-17T06:42:23+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>2887858+deivid-rodriguez@users.noreply.github.com</email>
</author>
<published>2025-09-09T17:20:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=7c5613a63865553c4191e82249c157e8a16eca75'/>
<id>7c5613a63865553c4191e82249c157e8a16eca75</id>
<content type='text'>
For consistency with the other deprecations.

https://github.com/rubygems/rubygems/commit/28e300cee1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
For consistency with the other deprecations.

https://github.com/rubygems/rubygems/commit/28e300cee1
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Completely remove multisources support</title>
<updated>2025-09-16T08:17:32+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>2887858+deivid-rodriguez@users.noreply.github.com</email>
</author>
<published>2025-09-09T17:18:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=6adcc5596884619e386d5412e94ef4443868b94f'/>
<id>6adcc5596884619e386d5412e94ef4443868b94f</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/8f9d6c54a1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/8f9d6c54a1
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Complete remembered options removal</title>
<updated>2025-09-11T02:54:49+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>2887858+deivid-rodriguez@users.noreply.github.com</email>
</author>
<published>2025-09-09T12:37:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=ecd1284bf246ae739890d154706f4f533bc8d77e'/>
<id>ecd1284bf246ae739890d154706f4f533bc8d77e</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/573ffad3ea
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/573ffad3ea
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Fix `bundle cache` failing in frozen mode if vendor/cache is empty</title>
<updated>2025-09-03T14:38:37+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2025-08-13T17:36:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=2558350c0488ccd1a71b5f1e86f7fdbccad5056e'/>
<id>2558350c0488ccd1a71b5f1e86f7fdbccad5056e</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/36c5af9156
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/36c5af9156
</pre>
</div>
</content>
</entry>
<entry>
<title>Cancel `--force` deprecation in favor of `--redownload`</title>
<updated>2025-07-17T02:10:46+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2025-07-15T11:35:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=60fca1defc4b730877a474efeb0f22f39dce9af7'/>
<id>60fca1defc4b730877a474efeb0f22f39dce9af7</id>
<content type='text'>
I realized `--redownload` is not a good name, because it does not
necessarily redownloads gems. It only forces reinstallation even if gem
is already installed.

So I believe `--force` is actually a better name and the introduction of
`--force` was a misunderstanding of what the `--force` flag did at the
time.

Let's cancel the deprecation of `--force`.

For now the `--redownload` alias is left around until we decide what to
do with it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I realized `--redownload` is not a good name, because it does not
necessarily redownloads gems. It only forces reinstallation even if gem
is already installed.

So I believe `--force` is actually a better name and the introduction of
`--force` was a misunderstanding of what the `--force` flag did at the
time.

Let's cancel the deprecation of `--force`.

For now the `--redownload` alias is left around until we decide what to
do with it.
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Cancel `path_relative_to_cwd` change</title>
<updated>2025-07-07T02:53:11+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2025-07-02T07:31:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=cd3389e5c25489e426b891ea673a483fdca1b2ce'/>
<id>cd3389e5c25489e426b891ea673a483fdca1b2ce</id>
<content type='text'>
It only affected the `--path` flag which is actually getting removed, so
I don't think it makes sense to make such change. The current behavior
is reasonable and I tried to codify it with a few more specs.

https://github.com/rubygems/rubygems/commit/6f520eb146
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It only affected the `--path` flag which is actually getting removed, so
I don't think it makes sense to make such change. The current behavior
is reasonable and I tried to codify it with a few more specs.

https://github.com/rubygems/rubygems/commit/6f520eb146
</pre>
</div>
</content>
</entry>
</feed>
