gstack/bin
Francois Aubert 56596f5b43 fix(update-check): --force now clears snooze so user can upgrade after snoozing
When a user snoozes an upgrade notification but then changes their mind
and runs `/gstack-upgrade` directly, the --force flag should allow them
to proceed. Previously, --force only cleared the cache but still respected
the snooze, leaving the user unable to upgrade until the snooze expired.

Now --force clears both cache and snooze, matching user intent: "I want
to upgrade NOW, regardless of previous dismissals."

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-03-19 16:06:49 +01: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-config feat: smart update check with auto-upgrade, snooze backoff, config CLI (v0.3.9) (#62) 2026-03-14 23:28:02 -07:00
gstack-diff-scope fix: security hardening + issue triage (v0.8.3) (#205) 2026-03-19 01:58:43 -05:00
gstack-review-log fix: atomic review log helpers + platform-agnostic templates (v0.8.5) (#209) 2026-03-19 00:47:11 -07:00
gstack-review-read fix: atomic review log helpers + platform-agnostic templates (v0.8.5) (#209) 2026-03-19 00:47:11 -07:00
gstack-slug fix: security hardening + issue triage (v0.8.3) (#205) 2026-03-19 01:58:43 -05:00
gstack-update-check fix(update-check): --force now clears snooze so user can upgrade after snoozing 2026-03-19 16:06:49 +01:00