@seanyao/roll 2.602.4 → 2.602.5

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## v2.602.5
+
+### 稳定性
+
+- **升级后彻底不再反向提示"升级"回旧版本(FIX-170)** — 续 FIX-166:上次清缓存只在「新版本自己跑升级」时生效,可升级其实是旧版本执行的,所以换版本后偶尔还会被叫去装回旧号(这回升到 2.602.4 又冒出来提示装回 2.602.2)。现在版本检查缓存绑定了写它的版本号,版本一变缓存立即失效,不管 roll update / npm / brew / 手动哪种升级方式都不会再反向提示
+
 ## v2.602.4
 
 ### 可见性

package/bin/roll

@@ -4,7 +4,7 @@ set -euo pipefail
 # Roll — AI Agent Convention Manager
 # Single source of truth for how all AI coding agents behave.
 
-VERSION="2.602.4"
+VERSION="2.602.5"
 ROLL_HOME="${ROLL_HOME:-${HOME}/.roll}"
 ROLL_CONFIG="${ROLL_HOME}/config.yaml"
 ROLL_GLOBAL="${ROLL_HOME}/conventions/global"
@@ -15576,19 +15576,30 @@ _invalidate_update_cache() {
   rm -f "${ROLL_HOME}/.update-check"
 }
 
+# FIX-170: the cache file is `<ts> <latest> <writer-version>` — the 3rd field
+# binds it to the binary version that wrote it. FIX-166's explicit invalidation
+# only covers `roll update` run by a NEW binary; an upgrade executed by an old
+# binary (the 2.602.2→2.602.4 transition) or out-of-band (npm -g / brew / git)
+# left a stale cache that reverse-nagged for up to 24h. A writer-version
+# mismatch now means "stale" regardless of TTL: refetch, and stay silent until
+# the refetch lands. Legacy 2-field caches have no writer → auto-invalidated.
 _check_update_async() {
   local cache="${ROLL_HOME}/.update-check"
   local now; now=$(date +%s)
-  local last=0
-  [[ -f "$cache" ]] && last=$(awk '{print $1}' "$cache" 2>/dev/null || echo 0)
-  (( now - last < 86400 )) && return
+  local last=0 writer=""
+  if [[ -f "$cache" ]]; then
+    last=$(awk '{print $1}' "$cache" 2>/dev/null || echo 0)
+    writer=$(awk '{print $3}' "$cache" 2>/dev/null || true)
+  fi
+  [[ "$writer" == "$VERSION" ]] && (( now - ${last:-0} < 86400 )) && return
 
   {
     local latest
     latest=$(curl -sf --max-time 5 \
       "https://api.github.com/repos/seanyao/roll/releases/latest" \
       | grep '"tag_name"' | sed 's/.*"v\([^"]*\)".*/\1/' 2>/dev/null || true)
-    echo "$now ${latest:-}" > "$cache"
+    # `-` placeholder keeps the field positions stable when the fetch fails.
+    echo "$now ${latest:--} $VERSION" > "$cache"
   } &
   disown
 }
@@ -15596,8 +15607,13 @@ _check_update_async() {
 _notify_update() {
   local cache="${ROLL_HOME}/.update-check"
   [[ -f "$cache" ]] || return 0
-  local latest; latest=$(awk '{print $2}' "$cache" 2>/dev/null || true)
-  [[ -z "$latest" || "$latest" == "$VERSION" ]] && return
+  local latest writer
+  latest=$(awk '{print $2}' "$cache" 2>/dev/null || true)
+  writer=$(awk '{print $3}' "$cache" 2>/dev/null || true)
+  # FIX-170: cache written by a different binary version is stale — stay
+  # silent; _check_update_async has already kicked off the refetch.
+  [[ "$writer" != "$VERSION" ]] && return
+  [[ -z "$latest" || "$latest" == "-" || "$latest" == "$VERSION" ]] && return
   # FIX-163: the cached `latest` is GitHub's releases/latest — the newest
   # release by created_at, NOT by semver. Under the MAJOR.MMDD scheme a plain
   # `sort -V` mis-ranks versions across the year-based→MAJOR.MMDD transition

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seanyao/roll",
-  "version": "2.602.4",
+  "version": "2.602.5",
   "description": "Roll — Roll out features with AI agents",
   "scripts": {
     "test": "bash tests/run.sh"