gstack/browse
Garry Tan baf8acd55c
fix: update check ignores stale UP_TO_DATE cache after version change
The UP_TO_DATE cache path exited immediately without checking if the
cached version still matched the local VERSION. After upgrading (e.g.
0.3.3 → 0.3.4), the cache still said "UP_TO_DATE 0.3.3" and the
script never re-checked against remote — so updates were invisible
until the 24h cache expired.

Now both UP_TO_DATE and UPGRADE_AVAILABLE verify cached version vs
local before trusting the cache.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-14 13:23:25 -05:00
..
bin Merge remote-tracking branch 'origin/main' into v0.3.6-qa-upgrades 2026-03-14 02:35:48 -05:00
src Merge remote-tracking branch 'origin/main' into v0.3.6-qa-upgrades 2026-03-14 02:35:48 -05:00
test fix: update check ignores stale UP_TO_DATE cache after version change 2026-03-14 13:23:25 -05:00
SKILL.md fix: browse binary discovery broken for agents (v0.3.5) (#44) 2026-03-14 00:24:06 -07:00
SKILL.md.tmpl fix: browse binary discovery broken for agents (v0.3.5) (#44) 2026-03-14 00:24:06 -07:00