ruby.git/spec/bundler/commands/outdated_spec.rb, branch v3_4_9 The Ruby Programming Language Merge RubyGems-3.6.6 and Bundler-2.6.6 2025-04-09T00:54:29+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2025-04-09T00:19:10+00:00 db2bf9f078c21b9e0234a736214ed74642d9f795 






Merge RubyGems-3.6.3 and Bundler-2.6.3
2025-02-21T00:50:20+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2025-02-21T00:27:17+00:00

19c69f382baa13cac3bf36b861067bdc424e1be1












[rubygems/rubygems] Fix `bundle outdated` with `--group` option
2024-09-23T10:37:57+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2024-09-20T13:37:52+00:00

c071fedb320d8e7c9edc3087a3386895d59c6100

It was printing incorrect output and returning incorrect status.

https://github.com/rubygems/rubygems/commit/96f5979c7d





It was printing incorrect output and returning incorrect status.

https://github.com/rubygems/rubygems/commit/96f5979c7d







[rubygems/rubygems] Emit progress to stderr when `--parseable` is passed to `bundle outdated`
2024-08-30T10:36:08+00:00

Matt Brictson
matt@mattbrictson.com

2024-08-24T21:16:59+00:00

830ff66e2c7315470580dd8531f4c10b0200aed5

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





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







[rubygems/rubygems] Extract a `build_repo3` helper
2024-08-05T17:27:11+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2024-08-02T19:36:08+00:00

dc804bd83c79d39eac71ca1a369061a8ba1b4ace

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





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







Synchronize Bundler & RubyGems (#11071)
2024-06-28T14:12:29+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2024-06-28T14:12:29+00:00

98c923ff4bbeeb4a8f9f63ea2695a38471da42c2












[rubygems/rubygems] Use modern hashes consistently
2023-12-07T22:29:33+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2023-12-07T21:10:33+00:00

2755cb1b2fbc4a5f08ca56345b5945bd452da74e

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





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







[rubygems/rubygems] Remove unnecessary `specific_local_platform` test helper
2023-03-17T09:50:55+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2023-03-13T17:57:38+00:00

d5121992dc50112e0ebae84b993a957fdcdcff45

https://github.com/rubygems/rubygems/commit/86b574824d





https://github.com/rubygems/rubygems/commit/86b574824d







[rubygems/rubygems] Fix `bundle outdated --strict`
2022-08-03T07:33:53+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2022-08-01T15:11:20+00:00

851b3aa7dde489502f517cc1ad9d31d9a3056197

It should be an alias of `--filter-strict`.

`--update-strict` is essentially a dummy option with no special behavior
associated and should be deprecated.

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





It should be an alias of `--filter-strict`.

`--update-strict` is essentially a dummy option with no special behavior
associated and should be deprecated.

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







[rubygems/rubygems] Fix conservative updates regardless of `--strict`
2022-08-03T07:33:52+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2022-08-01T14:41:31+00:00

35c65e7ba6b4aa8bc80aaca8429a48c4eb923b89

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





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