BUNDLE-OUTDATED(1)

πŸ“¦ version 4.0.6, in centos-stream 10

πŸ’… bundle-outdated β€” like, which of ur gems are sooo behind? πŸ‘‘

okay so this is bundle-outdated from the General Commands Manual section, and bestie, it's literally the tool that tells u which of ur installed gems have shiny newer versions waiting for u. no cap. πŸŽ€


✨ SYNOPSIS ✨

bundle outdated [GEM] [--local] [--pre] [--source] [--filter-strict |
--strict] [--update-strict] [--parseable | --porcelain] [--group=GROUP]
[--groups] [--patch|--minor|--major] [--filter-major] [--filter-minor]
[--filter-patch] [--only-explicit] [--cooldown=NUMBER]

πŸ¦‹ DESCRIPTION πŸ¦‹

Outdated lists the names and versions of gems that have a newer version available in the given source. that's it, that's the whole vibe check πŸ”₯

if u call outdated with [GEM [GEM]], it only checks for newer versions of the gems u actually named. like, stay in ur lane, other gems. πŸ™ˆ

prerelease gems are ignored by default (iconic behavior honestly).

and here's the exit-status tea β˜•: if ur gems are all up to date, Bundler exits with a status of 0. otherwise? it exits 1. so yeah, 1 means "bestie u have work to do". 😭


🌸 OPTIONS 🌸

  • --local β€” do NOT try to fetch gems remotely, just use the gem cache instead. cozy, offline, no network drama. 🧚
  • --pre β€” check for newer pre-release gems too. living on the edge, we love that for u.
  • --source=<list> β€” check against one specific source. picky queen behavior. πŸ‘‘
  • --filter-strict, --strict β€” only list newer versions that ur Gemfile requirements actually allow, and also respect the conservative update flags (--patch, --minor, --major). rules are rules πŸ’…
  • --update-strict β€” strict conservative resolution: do not let any gem get updated past the latest --patch | --minor | --major. literally no sneaking past the boundary. 🚧
  • --parseable, --porcelain β€” minimal formatting so the output is more parseable. for when u want the data, not the aesthetics. πŸ€–
  • --group=GROUP β€” list gems from one specific group.
  • --groups β€” list gems organized by their groups. so organized, so aesthetic. πŸŽ€
  • --minor β€” prefer updating only to the next minor version.
  • --major β€” prefer updating to the next major version (this is the default btw, main character energy 🫢).
  • --patch β€” prefer updating only to the next patch version.
  • --filter-major β€” only list major newer versions.
  • --filter-minor β€” only list minor newer versions.
  • --filter-patch β€” only list patch newer versions.
  • --only-explicit β€” only list gems specified in ur Gemfile, not their dependencies. no plus-ones allowed πŸ™…β€β™€οΈ
  • --cooldown=<number> β€” annotate (rather than hide!) versions that are still inside the cooldown window of number days. the prose output appends "in cooldown for Nd more days" and the table form adds "(cooldown Nd)" to the Latest column. see cooldown in bundle-config(1). 🧊

πŸŽ€ PATCH LEVEL OPTIONS πŸŽ€

see bundle update(1) bundle-update.1.html for the details, bestie β€” they're all over there.


🌈 FILTERING OUTPUT 🌈

important note before we go any further: the 3 filtering options do not affect the resolution of versions, they merely change what versions are shown in the output. so like, they're cosmetic. the resolution stays exactly the same. periodt. πŸ’…

if the regular output shows this:

* Gem       Current  Latest  Requested  Groups              Release Date
* faker     1.6.5    1.6.6   ~> 1.4     development, test   2024-02-05
* hashie    1.2.0    3.4.6   = 1.2.0    default             2023-11-10
* headless  2.2.3    2.3.1   = 2.2.3    test                2022-08-19

then --filter-major would only show:

* Gem       Current  Latest  Requested  Groups   Release Date
* hashie    1.2.0    3.4.6   = 1.2.0    default  2023-11-10

and --filter-minor would only show:

* Gem       Current  Latest  Requested  Groups  Release Date
* headless  2.2.3    2.3.1   = 2.2.3    test    2022-08-19

and --filter-patch would only show:

* Gem       Current  Latest  Requested  Groups              Release Date
* faker     1.6.5    1.6.6   ~> 1.4     development, test   2024-02-05

and here's the fun part β€” filter options can be combined! 🫢 so --filter-minor and --filter-patch together would show:

* Gem       Current  Latest  Requested  Groups              Release Date
* faker     1.6.5    1.6.6   ~> 1.4     development, test   2024-02-05

and combining all three filter options? that gives u the same result as providing none of them at all. 😭 full circle, we love a symmetry moment.


ngl, that's literally the whole page. go forth and check ur gems bestie πŸ’–

okok and the cute sign-off: this lil beauty is from the April 2026 release, BUNDLE-OUTDATED(1) β€” slay, see u next time! 🌟

πŸ“¦ where this page comes from
  • centos-stream 10: ruby4.0 4.0.6-37.el10 Β· (Ruby OR BSD-2-Clause) AND (Ruby OR BSD-2-Clause OR GPL-1.0-or-later) AND BSD-3-Clause AND (GPL-3.0-or-later WITH Bison-exception-2.2) AND ISC AND LicenseRef-Fedora-Public-Domain AND MIT AND CC0-1.0 AND zlib AND Unicode-DFS-2015 AND HPND-Markus-Kuhn AND Ruby-pty AND (Ruby OR BSD-2-Clause OR Python-2.0.1) AND BSD-2-Clause AND (Apache-2.0 OR BSL-1.0) AND GPL-2.0-only AND CC-BY-2.5 AND OFL-1.1-RFN AND BSL-1.0
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms