CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-05-07 14:06:42 +02:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
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>
This commit is contained in:
Francois Aubert
2026-03-19 16:06:49 +01:00
parent bd834aeadb
commit 56596f5b43
2 changed files with 20 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bin/gstack-update-check
+2 -1
View File
@@ -20,9 +20,10 @@ SNOOZE_FILE="$STATE_DIR/update-snoozed"
VERSION_FILE="$GSTACK_DIR/VERSION"
REMOTE_URL="${GSTACK_REMOTE_URL:-https://raw.githubusercontent.com/garrytan/gstack/main/VERSION}"
# ─── Force flag (busts cache for standalone /gstack-upgrade) ──
# ─── Force flag (busts cache + snooze for standalone /gstack-upgrade) ──
if [ "${1:-}" = "--force" ]; then
rm -f "$CACHE_FILE"
rm -f "$SNOOZE_FILE"
fi
# ─── Step 0: Check if updates are disabled ────────────────────