`Upgrades` tab is stuck in an outdated state

[SMillerDev]

Before submitting

• I have searched the issues and pull requests for duplicates.
• I am reporting a specific problem with BrewUI and have described how to reproduce it, or the circumstances of an intermittent failure.

What happened?

The Upgrades tab only reports 2 upgrades, no matter the amount of upgrades available in the CLI.

Expected behaviour

The Upgrades tab shows the same upgrades as brew outdated.

Steps to reproduce

1. Open Upgrades tab
2. Compare to brew outdated

App version and build

Version 0.4.3 (1106)

How was the app installed?

Homebrew cask

macOS version and build

26.6.2 (25G83)

Mac processor

Apple silicon

Homebrew configuration

Homebrew
HOMEBREW_VERSION: 7.0.4-13-g8636847
ORIGIN: https://github.com/Homebrew/brew
HEAD: 8636847fb47d2b26c1655be3df0ebb0144fe0dc1
Last commit: 3 hours ago
Branch: main
Core tap JSON: 16 Sep 07:12 UTC
HOMEBREW_PREFIX: /opt/homebrew
Homebrew Ruby: 4.0.7 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/4.0.7/bin/ruby

System
Core tap HEAD: 69239163bf1d89593cf08fdf91b62da16abab098
Core tap last commit: 27 minutes ago
Core cask tap HEAD: 55c7e1ddd91ac7242aa27586a52febb5b65ad76c
Core cask tap last commit: 32 minutes ago
CPU: deca-core 64-bit arm_hidra
Clang: 21.0.0 build 2100
Git: 2.55.0 => /opt/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 26.6.2-arm64
CLT: 27.0.0.0.1788430756
Xcode: N/A
Rosetta 2: false

Environment (HOMEBREW_*)
HOMEBREW_VERSION: 7.0.4-13-g8636847
HOMEBREW_PREFIX: /opt/homebrew

Logs, screenshots and crash reports

Additional context

No response

[SMillerDev]

After running an upgrade through the app, it now shows the correct amount of upgrades:

[graeme]

@SMillerDev : Did the incorrect upgrades amount show even when you hit Cmd+R? This could just be a caching issue so, if the experience felt off to you, we could tweak the refresh rate.

[SMillerDev]

I didn't know that key combo, but no amount of pressing Refresh in the UI over multiple days made any difference.

It's not just the amount by the way, the listing was also wrong.

[pbadams]

I have the same issue. The upgrades tab only updates if I run brew upgrade manually on the command line.

Homebrew
HOMEBREW_VERSION: 7.0.4
ORIGIN: https://github.com/Homebrew/brew
HEAD: edb70f031e4170c780799633a1226ff73e1077f4
Last commit: 3 days ago
Branch: stable
HOMEBREW_PREFIX: /opt/homebrew
Homebrew Ruby: 4.0.7 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/4.0.7/bin/ruby

System
Core tap HEAD: 2d277fc6ccf095dff8b35309713505bb51415b54
Core tap last commit: 50 minutes ago
Core cask tap: N/A
CPU: dodeca-core 64-bit arm_blizzard_avalanche
Clang: 21.0.0 build 2100
Git: 2.54.0 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 27.0-arm64
CLT: 27.0.0.0.1788430756
Xcode: 27.0
Metal Toolchain: N/A
Rosetta 2: false

Environment (HOMEBREW_*)
HOMEBREW_VERSION: 7.0.4
HOMEBREW_PREFIX: /opt/homebrew

[graeme]

@SMillerDev The upgrades list comes from the brew info --installed json=v2. So my suspicion is either that that command is failing for some reason or that its cache replacement policy is different. Unless there's some other reason you can think of why that would be a flawed source of truth for the upgrades list?

@SMillerDev @pbadams If you experience this again / are still experiencing it, would you mind checking if your brew info --installed CLI output is also out of date?

In the meantime, I'll probably need to ship some more useful logs as, if the command is failing for some reason, I'd like to know why and make sure I'm handling properly. The config output alone isn't telling me much. Stay tuned...

[SMillerDev]

The upgrades list comes from the brew info --installed json=v2. So my suspicion is either that that command is failing for some reason or that its cache replacement policy is different. Unless there's some other reason you can think of why that would be a flawed source of truth for the upgrades list?

Do you run brew update before? Otherwise I don't think it would ever know about updates. While I think brew outdated --json pulls updates when you run it.

[pbadams]

@graeme

If you experience this again / are still experiencing it, would you mind checking if your brew info --installed CLI output is also out of date?

I ran brew info --installed, copied output into VS Code and searched for ==> and saw 120 occurrences. In the app, Installed showed 119 packages under all. Updates tab was empty. Ran brew upgrade and responded n to the 4 packages requiring upgrade, then restarted app. Installed tab still showed 119 all packages (FWIW) and the 4 packages showed up in the Updates tab.

Definitely concur that some command logging would help problem determination.

BTW is there anything that should be specified in brew.env that might impact app behaviour? The documentation is sparse on the subject.

[pbadams]

brew info --installed json=v2

That command doesn't produce JSON and I was trying to count command line output.

Running brew info --json=v2 --installed gives me 89 formulae and 31 casks, which matches the installed tab.

[Kristofp]

When you run upgrade it doesn't first do an update of homebrew so it sees nothing has changed and doesn't offer any packages for upgrading, so either add an update button or run it before upgrade

[MikeMcQuaid]

When you run upgrade it doesn't first do an update of homebrew

brew upgrade runs brew update.

[Kristofp]

When you run upgrade it doesn't first do an update of homebrew

brew upgrade runs brew update.

That's odd because I had to run it in the terminal manually before the upgrade button did anything.

[dergachoff]

Same here. No amount of refreshing updates "Upgrade" tab for me.

It only updates during brew upgrade

[SMillerDev]

It really seems like the upgrade button is just missing a brew update call. Once I do that in the terminal the app works as expected. This is because brew info --installed --json=v2 does not perform any data updates in the background, so it will only show the data from the last time a command was ran that upgrades the package index.

Video showing update works: https://github.com/user-attachments/assets/225bd203-139c-4e77-aea6-e62dd45af568

[aakay]

When you run upgrade it doesn't first do an update of homebrew

brew upgrade runs brew update.

yes, but if there's nothing to upgrade yet (update missing, UI showing ✅ Everything is up to date), you can't run an update before upgrade -- unless you do it manually in terminal. My expectation would be the Refresh button to handle this case.