Fix stale cask upgrade metadata#22986
Merged
Merged
Conversation
- Prefer the installed metadata path version over a stale tab when loading saved JSON cask metadata. - This lets upgrades recover from receipts left behind by earlier successful cask upgrades. - Add a regression covering two consecutive `local-caffeine` upgrades.
8 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes an edge case in cask upgrades where the “installed version” can be incorrectly inferred from a stale INSTALL_RECEIPT.json (tab), causing subsequent upgrades to reference the wrong on-disk version directory and fail. The change makes installed-caskfile loading prefer the version encoded in the installed metadata path, and adds a regression test covering two consecutive upgrades.
Changes:
- Prefer the installed metadata path version (
.../.metadata/<version>/...) over the tab’s stored version when loading from an installed caskfile JSON. - Add a regression spec that installs an outdated cask, upgrades it, then upgrades it again to ensure installed version tracking stays correct.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| Library/Homebrew/cask/cask_loader.rb | Adjusts version resolution precedence when loading from an installed caskfile JSON to avoid stale tab versions. |
| Library/Homebrew/test/cask/upgrade_spec.rb | Adds a regression test validating two consecutive upgrades use the correct installed metadata version. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
p-linnane
approved these changes
Jul 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
local-caffeineupgrades.Closes #22983 with a different/simpler approach.
brewcommands to reproduce the bug?brew lgtm(style, typechecking and tests) locally?OpenAI Codex 5.5 xhigh with local review and testing.