`bundle outdated --filter-major --filter-minor --filter-patch` omits 4th-segment and prerelease-to-release updates
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
issueで示されている Bundler::CLI::Outdated#update_present_via_semver_portions から始め、spec.version.segments が各フィルターとどのように比較されるかを追ってください。bundle outdated のフィルタリングに関する既存のテストを読み、第4セグメントの更新と、プレリリースからリリースへの更新を対象とするテストを追加してください。パッチフィルターがこれらの更新を報告し、3つすべてのフィルターを組み合わせた結果がフィルターなしの出力と一致すれば完了です。
索引モデルが issue の本文から書いたものです。
説明
Describe the problem as clearly as you can
bundle outdated --filter-patch (and even bundle outdated --filter-major --filter-minor --filter-patch) omits gems whose available update is in a 4th numeric segment (1.2.3 -> 1.2.3.1 or 1.2.3.4 -> 1.2.3.5, common for Rails and Nokogiri security releases) or from a prerelease to its final release (1.0.0.rc1 -> 1.0.0), even though plain bundle outdated lists them and GemVersionPromoter#filter_versions treats updates with matching major and minor segments as patch-level updates. When all outdated gems are of these forms, bundle outdated --filter-patch prints No patch updates to display. and exits 0.
In Bundler::CLI::Outdated#update_present_via_semver_portions, only indices 0, 1, and 2 of spec.version.segments (coerced with .to_i) are compared, so [1, 2, 3] vs [1, 2, 3, 1], [1, 2, 3, 4] vs [1, 2, 3, 5], and [1, 0, 0, "rc", 1] vs [1, 0, 0] all compare equal across major, minor, and patch and match none of the three filters.
Did you try upgrading rubygems & bundler?
Yes. Reproduced on RubyGems / Bundler 4.1.0 (Ruby 4.0.9) and on ruby/rubygems master (5879ffe34b67, 4.2.0.dev).
Post steps to reproduce the problem
mkdir /tmp/repro-outdated-filter && cd /tmp/repro-outdated-filter
mkdir -p repo/gems repo/quick/Marshal.4.8 app
ruby - << 'RUBY'
require "rubygems/package"
require "zlib"
specs = [
["aa", "1.2.3"], ["aa", "1.2.3.1"],
["bb", "1.2.3.4"], ["bb", "1.2.3.5"],
["cc", "1.0.0.rc1"], ["cc", "1.0.0"],
["dd", "1.2.3"], ["dd", "1.2.4"],
].map do |name, ver|
Gem::Specification.new do |s|
s.name = name; s.version = ver; s.summary = name; s.authors = ["test"]
end
end
specs.each do |s|
gem_file = Gem::Package.build(s, true)
File.rename(gem_file, "repo/gems/" + gem_file)
File.binwrite("repo/quick/Marshal.4.8/" + s.original_name + ".gemspec.rz",
Zlib::Deflate.deflate(Marshal.dump(s)))
end
rel, pre = specs.partition { |s| !s.version.prerelease? }
File.binwrite("repo/specs.4.8.gz",
Zlib.gzip(Marshal.dump(rel.map { |s| [s.name, s.version, "ruby"] })))
File.binwrite("repo/prerelease_specs.4.8.gz",
Zlib.gzip(Marshal.dump(pre.map { |s| [s.name, s.version, "ruby"] })))
RUBY
cat > app/Gemfile <<GEMFILE
source "file://$PWD/repo"
gem "aa", "1.2.3"
gem "bb", "1.2.3.4"
gem "cc", "1.0.0.rc1"
gem "dd", "1.2.3"
GEMFILE
cd app
bundle config set --local path vendor/bundle
bundle install
cat > Gemfile <<GEMFILE
source "file://$(dirname "$PWD")/repo"
gem "aa"
gem "bb"
gem "cc", ">= 1.0.0.rc1"
gem "dd"
GEMFILE
bundle outdated
bundle outdated --filter-major --filter-minor --filter-patch
bundle outdated --filter-patch aa bb cc
Which command did you run?
bundle outdated --filter-major --filter-minor --filter-patch and bundle outdated --filter-patch aa bb cc
What were you expecting to happen?
bundle outdated --filter-major --filter-minor --filter-patch should list aa, bb, cc, and dd, matching bundle outdated (bundle-outdated(1) states under FILTERING OUTPUT at https://bundler.io/man/bundle-outdated.1.html that combining all three filter options produces the same result as providing none of them), and bundle outdated --filter-patch aa bb cc should list aa, bb, and cc and exit 1.
What happened instead?
$ bundle outdated
Fetching source index from file:///tmp/repro-outdated-filter/repo/
Resolving dependencies...
Gem Current Latest Requested Groups Release Date
aa 1.2.3 1.2.3.1 >= 0 default
bb 1.2.3.4 1.2.3.5 >= 0 default
cc 1.0.0.rc1 1.0.0 >= 1.0.0.rc1 default
dd 1.2.3 1.2.4 >= 0 default
$ bundle outdated --filter-major --filter-minor --filter-patch
Fetching source index from file:///tmp/repro-outdated-filter/repo/
Resolving dependencies...
Gem Current Latest Requested Groups Release Date
dd 1.2.3 1.2.4 >= 0 default
$ bundle outdated --filter-patch aa bb cc
Fetching source index from file:///tmp/repro-outdated-filter/repo/
Resolving dependencies...
Resolving dependencies...
No patch updates to display.
bundle outdated --filter-patch aa bb cc exits with status 0.
If not included with the output of your command, run bundle env and paste the output below
## Environment
```
Bundler 4.1.0
Platforms ruby, x86_64-linux
Ruby 4.0.9p0 (2026-10-23 revision 3e93b23afcec3433f6aecc34b5d832799d754238) [x86_64-linux]
Full Path /opt/ruby-4.0.9/bin/ruby
Config Dir /opt/ruby-4.0.9/etc
RubyGems 4.1.0
Gem Home /opt/ruby-4.0.9/lib/ruby/gems/4.0.0
Gem Path /home/user/.local/share/gem/ruby/4.0.0:/opt/ruby-4.0.9/lib/ruby/gems/4.0.0
User Home /home/user
User Path /home/user/.local/share/gem/ruby/4.0.0
Bin Dir /opt/ruby-4.0.9/bin
Git 2.39.5
```
## Bundler Build Metadata
```
Timestamp 2026-11-16
Git SHA 9af9267
```
## Bundler settings
```
path
Set for your local app (/tmp/repro-outdated-filter/app/.bundle/config): "vendor/bundle"
```
## Gemfile
### Gemfile
```ruby
source "file:///tmp/repro-outdated-filter/repo"
gem "aa"
gem "bb"
gem "cc", ">= 1.0.0.rc1"
gem "dd"
```
### Gemfile.lock
```
GEM
remote: file:///tmp/repro-outdated-filter/repo/
specs:
aa (1.2.3)
bb (1.2.3.4)
cc (1.0.0.rc1)
dd (1.2.3)
PLATFORMS
ruby
x86_64-linux
DEPENDENCIES
aa (= 1.2.3)
bb (= 1.2.3.4)
cc (= 1.0.0.rc1)
dd (= 1.2.3)
CHECKSUMS
aa (1.2.3) sha256=f80a3cf7e6036565271104ca8456835abf7e995d5b26b8895868efd36eec990d
bb (1.2.3.4) sha256=c0926288182253e9a7cffeb968d07056925b153d69818ac2597ae2dc0c993e11
cc (1.0.0.rc1) sha256=559e9a26bee896c492de1393b015f46df3390c9cbb3de7bbc7239ac76f8927e5
dd (1.2.3) sha256=3af7e397a5769cc5d58261f4a88d41283b109e1ee4fe7b9fbcb0eb54b92f17ee
BUNDLED WITH
4.1.0
```
Credit: https://ucsbplse.github.io/
- 主要言語
- Ruby
- スター
- 4k
- フォーク
- 2k
- 平均マージ
- 1日 21時間
- マージ済み PR(30日)
- 73
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
ruby/rubygems のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
RubyGems
難易度 3/5 1〜2日 初心者へのやさしさ 67/100
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 56/100
メンテナーはふだん 1 日以内に返信
似ている issue
-
難易度 1/5 1〜3時間 初心者へのやさしさ 66/100
philippe-nougaillon/coopcomm#543 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
we-promise/sure#5191 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
-
Source Support
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
palkan/action_policy#316 ·