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

..

dev-setup

feat: SKILL.md template system, 3-tier testing, DX tools (v0.3.3) (#41)

2026-03-13 21:08:12 -07:00

dev-teardown

feat: v0.3.2 — project-local state, diff-aware QA, Greptile integration (#36)

2026-03-13 18:10:56 -07:00

gstack-update-check

fix: update check ignores stale UP_TO_DATE cache after version change

2026-03-14 13:23:25 -05:00