`bundle outdated --filter-major --filter-minor --filter-patch` omits 4th-segment and prerelease-to-release updates

Open Beginner friendly
#10,086 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
ruby
Domain
cli

Research direction

Start in Bundler::CLI::Outdated#update_present_via_semver_portions, identified in the issue, and trace how spec.version.segments are compared with each filter. Read the existing tests for bundle outdated filtering and add coverage for fourth-segment and prerelease-to-release updates. Done means patch filtering reports those updates and combining all three filters matches unfiltered output.

Written by the indexing model from the issue text.

Description

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/

Dominant language
Ruby
Stars
4k
Forks
2k
Avg merge
1d 20h
Merged PRs (30d)
75

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/rubygems

All issues in ruby/rubygems

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.