Open
Conversation
Two bugs in bin/gstack-update-check: 1. --force did not clear the marker file, so forced checks still short-circuited on a stale just upgraded marker. 2. The marker handler wrote UP_TO_DATE to cache and exited, never checking if an even newer version was available on remote. Now: marker handler prints JUST_UPGRADED but falls through to the remote check. --force clears both cache and marker. The marker handler also clears the cache to prevent stale cache entries from suppressing the remote check. Adds 4 regression tests covering --force+marker, marker+newer remote, marker+same remote, and marker+fresh cache scenarios.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
No description provided.