fix(upgrade): refresh outdated cache after upgrades - #44
Merged
Merged
Conversation
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.
📝 Description
Fix a regression where
keg upgrade -asuccessfully upgraded packages, butkeg upgrade -accontinued reporting them as outdated.The outdated Homebrew snapshot was cached for up to 24 hours and was not refreshed after upgrades. The cache is now refreshed once after all successful upgrades complete.
A regression test was added to verify that
brew outdated --json=v2is executed and the cache is persisted.🔗 Related Issue(s)
🔄 Type of Change
📋 Checklist
📸 Screenshots (if applicable)
Not applicable.
🔍 Additional Notes
This is a non-breaking corrective release. The outdated cache is
refreshed once after the upgrade operation completes, avoiding
stale upgrade status while keeping the normal check path cached.