<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ruby.git/lib/bundler/ui/shell.rb, branch v3_4_9</title>
<subtitle>The Ruby Programming Language</subtitle>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/'/>
<entry>
<title>[rubygems/rubygems] Emit progress to stderr when `--parseable` is passed to `bundle outdated`</title>
<updated>2024-08-30T10:36:08+00:00</updated>
<author>
<name>Matt Brictson</name>
<email>matt@mattbrictson.com</email>
</author>
<published>2024-08-24T21:16:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=830ff66e2c7315470580dd8531f4c10b0200aed5'/>
<id>830ff66e2c7315470580dd8531f4c10b0200aed5</id>
<content type='text'>
Before, `bundle outdated --parseable` (or `--porcelain`) caused output
to be completely silenced during definition resolution, so nothing was
printed at all until the table of outdated gems was printed.

With this change, `--parseable`/`--porcelain` now prints progress to
stderr during resolution. E.g.:

```
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
```

This provides a better user experience, especially when
`outdated --parseable` takes several seconds or more.

The report of outdated gems is still printed to stdout, and the exit
status codes are unchanged, so the fundamental contract with other tools
consuming the `outdated --parseable` result should not be affected.

https://github.com/rubygems/rubygems/commit/7d4bb43570
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Before, `bundle outdated --parseable` (or `--porcelain`) caused output
to be completely silenced during definition resolution, so nothing was
printed at all until the table of outdated gems was printed.

With this change, `--parseable`/`--porcelain` now prints progress to
stderr during resolution. E.g.:

```
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
```

This provides a better user experience, especially when
`outdated --parseable` takes several seconds or more.

The report of outdated gems is still printed to stdout, and the exit
status codes are unchanged, so the fundamental contract with other tools
consuming the `outdated --parseable` result should not be affected.

https://github.com/rubygems/rubygems/commit/7d4bb43570
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Emit progress to stderr when `--print` is passed to `bundle lock`</title>
<updated>2024-08-26T14:56:26+00:00</updated>
<author>
<name>Matt Brictson</name>
<email>matt@mattbrictson.com</email>
</author>
<published>2024-08-23T00:29:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=7c794c287ec727f4634579556228cc018056e6f9'/>
<id>7c794c287ec727f4634579556228cc018056e6f9</id>
<content type='text'>
`bundle lock --print --update` can take a long time to fetch sources and
resolve the lock file.

Before, `--print` caused output to be completely silenced, so nothing
was printed at all until the resolved lock file is finally emitted to
stdout.

With this change, `--print` now prints progress to stderr. E.g.:

```
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
```

This provides a better user experience, especially when
`lock --print --update` takes several seconds or more.

The lock file is still printed to stdout, so tools consuming the lock
file on stdout will not be affected.

https://github.com/rubygems/rubygems/commit/6719baa700
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
`bundle lock --print --update` can take a long time to fetch sources and
resolve the lock file.

Before, `--print` caused output to be completely silenced, so nothing
was printed at all until the resolved lock file is finally emitted to
stdout.

With this change, `--print` now prints progress to stderr. E.g.:

```
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
```

This provides a better user experience, especially when
`lock --print --update` takes several seconds or more.

The lock file is still printed to stdout, so tools consuming the lock
file on stdout will not be affected.

https://github.com/rubygems/rubygems/commit/6719baa700
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Fix newline=false being ignored by Shell#warn</title>
<updated>2024-08-26T14:56:26+00:00</updated>
<author>
<name>Matt Brictson</name>
<email>matt@mattbrictson.com</email>
</author>
<published>2024-08-23T00:14:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=20664826840f1ae1ba83c97764996a71105212e5'/>
<id>20664826840f1ae1ba83c97764996a71105212e5</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/e021ff33a8
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/e021ff33a8
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Fix missing 'msg' parameter in Shell#no?</title>
<updated>2024-08-26T14:56:25+00:00</updated>
<author>
<name>Matt Brictson</name>
<email>matt@mattbrictson.com</email>
</author>
<published>2024-08-23T00:12:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=cfad1f95d50c76cf66b8539a34b67cb72323848e'/>
<id>cfad1f95d50c76cf66b8539a34b67cb72323848e</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/ffe89a099a
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/ffe89a099a
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Use match? when regexp match data is unused</title>
<updated>2023-12-13T22:00:26+00:00</updated>
<author>
<name>Samuel Giddins</name>
<email>segiddins@segiddins.me</email>
</author>
<published>2023-12-13T11:46:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=baf2ec2ca8127cd610a3681a1e84ebcb404fe8f2'/>
<id>baf2ec2ca8127cd610a3681a1e84ebcb404fe8f2</id>
<content type='text'>
Improved performance / reduced allocations

https://github.com/rubygems/rubygems/commit/b04726c9a7
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Improved performance / reduced allocations

https://github.com/rubygems/rubygems/commit/b04726c9a7
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Update vendored thor to v1.3.0</title>
<updated>2023-10-19T20:02:47+00:00</updated>
<author>
<name>Samuel Giddins</name>
<email>segiddins@segiddins.me</email>
</author>
<published>2023-10-19T16:22:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=af222d4db27b018a5e4a406ec668c479c68c0446'/>
<id>af222d4db27b018a5e4a406ec668c479c68c0446</id>
<content type='text'>
See https://github.com/rails/thor/releases/tag/v1.3.0

https://github.com/rubygems/rubygems/commit/3c7165474b
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
See https://github.com/rails/thor/releases/tag/v1.3.0

https://github.com/rubygems/rubygems/commit/3c7165474b
</pre>
</div>
</content>
</entry>
<entry>
<title>Migrate our resolver engine to PubGrub</title>
<updated>2022-11-11T22:40:31+00:00</updated>
<author>
<name>Hiroshi SHIBATA</name>
<email>hsbt@ruby-lang.org</email>
</author>
<published>2022-11-11T21:00:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=0a9d51ee9d2b3d0111832e5ea1c8195a16e2f99b'/>
<id>0a9d51ee9d2b3d0111832e5ea1c8195a16e2f99b</id>
<content type='text'>
  https://github.com/rubygems/rubygems/pull/5960

  Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  https://github.com/rubygems/rubygems/pull/5960

  Co-authored-by: David Rodríguez &lt;deivid.rodriguez@riseup.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Error tracing should be printed to stderr</title>
<updated>2021-12-19T21:49:49+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2021-12-19T14:31:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=72db2e00d4edb7a0e316a5979316595a67069d97'/>
<id>72db2e00d4edb7a0e316a5979316595a67069d97</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/23178f7d7b
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/23178f7d7b
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge bundler-2.2.0.rc.2</title>
<updated>2020-10-15T08:19:02+00:00</updated>
<author>
<name>Hiroshi SHIBATA</name>
<email>hsbt@ruby-lang.org</email>
</author>
<published>2020-10-15T04:20:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=d386a58f6f1865aaa35eda5af55cff3ff3cca4ca'/>
<id>d386a58f6f1865aaa35eda5af55cff3ff3cca4ca</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[bundler/bundler] Respect color option when instantiating shells</title>
<updated>2019-08-03T00:29:55+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2019-05-24T18:28:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=580e165873c727b9248e1ba7d3ac0af9b121a235'/>
<id>580e165873c727b9248e1ba7d3ac0af9b121a235</id>
<content type='text'>
Thor's base shell will be memoized the first time it is set. So if we
instantiate a no-color shell first, further instantiations of a bundler
shell will be initialized with a no-color shell by default. This is
caused some sources specs to fail, depending on the order they run.

See for example https://travis-ci.org/bundler/bundler/builds/500328994.

What we do to fix it is to reset the shell unless no-color is explicitly
specified. That way, further instantiations will rerun thor's internal
logic to choose the default shell.

https://github.com/bundler/bundler/commit/786b5d9894
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Thor's base shell will be memoized the first time it is set. So if we
instantiate a no-color shell first, further instantiations of a bundler
shell will be initialized with a no-color shell by default. This is
caused some sources specs to fail, depending on the order they run.

See for example https://travis-ci.org/bundler/bundler/builds/500328994.

What we do to fix it is to reset the shell unless no-color is explicitly
specified. That way, further instantiations will rerun thor's internal
logic to choose the default shell.

https://github.com/bundler/bundler/commit/786b5d9894
</pre>
</div>
</content>
</entry>
</feed>
