Skip to content

fix(update-check): --force now clears snooze so user can upgrade after snoozing#220

Open
francoisaubert1 wants to merge 1 commit intogarrytan:mainfrom
francoisaubert1:fix/force-clears-snooze
Open

fix(update-check): --force now clears snooze so user can upgrade after snoozing#220
francoisaubert1 wants to merge 1 commit intogarrytan:mainfrom
francoisaubert1:fix/force-clears-snooze

Conversation

@francoisaubert1
Copy link

Summary

  • --force flag now clears both cache AND snooze file
  • Allows users who snoozed an upgrade to still run /gstack-upgrade directly when they change their mind

Evidence

When a user snoozes an upgrade ("Not now") but then 10 minutes later runs /gstack-upgrade, the --force flag only cleared the cache but still respected the snooze — leaving the user unable to upgrade until the snooze expired (24h-7d).

Pre-Landing Review

No issues found.

Test Coverage

  • Added 1 new test: --force clears snooze so user can upgrade after snoozing
  • All 33 tests pass (32 existing + 1 new)

Test plan

  • All bun tests pass (bun test browse/test/gstack-update-check.test.ts)
  • Manual verification: snooze active → --force → upgrade available

🤖 Generated with Claude Code

…r 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant