[Bug?]: Dependencies from `catalog:` are not upgraded using upgrade-interactive

[karl-run]

Self-service

• [ ] I'd be willing to implement a fix

Describe the bug

I have a dependency in my .yarnrc.yml defined as a catalog:

catalog:
  vitest: ^3.2.4

Running yarn upgrade-interactive shows the following:

$ yarn upgrade-interactive
 Press <up>/<down> to select packages.            Press <enter> to install.
 Press <left>/<right> to select versions.         Press <ctrl+c> to abort.

? Pick the packages you want to upgrade.          Current          Range            Latest

 >  vitest -------------------------------------- ◉ catalog: -----                  ◯ ^4.0.1 -------

Which doesn't seem quite right. And selecting the new version does not do anything.

Preferably upgrade-interactive could show catalog versions in a different section, perhaps.

To reproduce

1. Have any catalogue dependency in a package.json
2. Make sure it has a newer version
3. run yarn upgrade-interactive

Environment

System:
    OS: Linux 6.14 Ubuntu 25.04 25.04 (Plucky Puffin)
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 24.8.0 - /tmp/xfs-a23f052f/node
    Yarn: 4.10.3 - /tmp/xfs-a23f052f/yarn
    npm: 11.6.0 - /home/karl/.local/share/mise/installs/node/24.8.0/bin/npm
    bun: 1.3.0 - /home/karl/.local/share/mise/installs/bun/1.3.0/bin/bun
    Deno: 2.5.4 - /home/karl/.local/share/mise/installs/deno/2.5.4/bin/deno

Additional context

No response

[snebjorn]

Yep, please improve the upgrade-interactive experience.

It even reports upgrades where there are none