git-span 1.1.7 → 1.1.10

package/README.md

@@ -36,6 +36,19 @@ The store is bounded by a count-based sweep: stale non-live generations are swep
 
 A configured filter driver's resolved executable (e.g. a `git-lfs` install) is content-hashed to prove its identity as part of every state-token capture. That hash is a fact about a file on the local machine, not about any one repository, so it is memoized in a *second*, small, per-user SQLite database — separate from the per-repo drift cache above — at `$GIT_SPAN_CACHE_HOME/exe-digest.db`, defaulting to `$HOME/.cache/git-span/exe-digest.db` (mirrors the workspace's `$HOME/.cache/git-span/cargo-target/` per-user build-artifact directory). Every repository on a machine that shares the same filter executable reuses the same memoized digest instead of re-hashing it per clone. `GIT_SPAN_EXE_DIGEST_DB` overrides the database file path directly (useful for CI isolation). `GIT_SPAN_CACHE=0` disables this store too, exactly like the drift cache. Implemented in `src/resolver/core/exe_digest_store.rs`; safe to delete at any time (it is rebuilt lazily, fail-closed on any error — a missing or broken database just means every executable is re-hashed).
 
+### The daily update check
+
+On an interactive `git span` invocation, the CLI quietly notices whether the running binary or the installed Claude Code / Codex git-span plugin bundles have fallen behind the latest `git-span-v*` release from GitHub, and — at most once per 24 hours — prints a short informational note naming what is out of date plus the exact command to bring it current. Nothing blocks: the network fetch and plugin-cache scans run in a detached background child, the foreground command's latency and exit code are untouched, and the first run prints nothing (the reminder reports what the *previous* check stored). Check state lives in a third, per-user SQLite database beside the exe-digest store — `$GIT_SPAN_CACHE_HOME/update-check.db`, defaulting to `$HOME/.cache/git-span/update-check.db` — with the same path precedence and fail-closed bootstrap; an offline machine pays one failed fetch attempt per day. The note only informs, never updates. Every check run appends one diagnostic line to `update-check.log` beside the database — the audit trail that separates a clean check from a silently failing one.
+
+Suppression is fail-closed and two-layered: any one of the following silences the check and the note.
+
+- `GIT_SPAN_DISABLE_UPDATE_CHECK` — presence disables the check and the message entirely. Automated callers set it: the Claude Code and Codex hook plugins export it into every hook process, and future git-hook integrations should too.
+- Machine-readable output — commands whose effective output format is machine-readable (`--porcelain`, `--oneline`, `--format` other than human, `context`, `merge-driver`) never engage the check.
+- Non-TTY stdout — piped or scripted invocations (including the VS Code extension and the agent-hooks shell-outs) are silent regardless of the other layers.
+- Hidden internal subcommands (`__context-service`, `__update-check`) never engage or remind.
+
+The remaining vars are testing and isolation seams: `GIT_SPAN_UPDATE_CHECK_URL` overrides the releases-API endpoint the child fetches; `GIT_SPAN_UPDATE_CHECK_DB` overrides the `update-check.db` path directly (mirroring `GIT_SPAN_EXE_DIGEST_DB`); `GIT_SPAN_PLUGIN_CACHE_ROOT` overrides the base the Claude Code and Codex plugin-cache scans resolve under (`{root}/{claude,codex}/plugins/cache`), instead of `$HOME/.{claude,codex}/plugins/cache` (or `CLAUDE_CONFIG_DIR` / `CODEX_HOME` when set). Implemented in `src/update_check/`.
+
 ## Profiling
 
 Perf investigation tooling is documented in [Profiling `git span drift`](../../wiki/guides/profiling-git-span-drift.md):

package/man/git-span.1

@@ -1,7 +1,7 @@
 .\" GENERATED by gen-manpage. Do not edit by hand.
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH git-span 1  "git-span 1.1.7"
+.TH git-span 1  "git-span 1.1.10"
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
 .SH NAME
@@ -145,7 +145,7 @@ Print this message or the help of the given subcommand(s)
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
 .SH VERSION
-v1.1.7
+v1.1.10
 .SH EXAMPLES
 Anchor a new span alongside a code change:
 .PP

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "git-span",
-  "version": "1.1.7",
+  "version": "1.1.10",
   "bin": "bin/git-span.exe",
   "man": [
     "man/git-span.1"
@@ -27,11 +27,11 @@
     "scripts/postinstall.js"
   ],
   "optionalDependencies": {
-    "git-span-darwin-arm64": "1.1.7",
-    "git-span-darwin-x64": "1.1.7",
-    "git-span-linux-arm64": "1.1.7",
-    "git-span-linux-x64": "1.1.7",
-    "git-span-win32-x64": "1.1.7"
+    "git-span-darwin-arm64": "1.1.10",
+    "git-span-darwin-x64": "1.1.10",
+    "git-span-linux-arm64": "1.1.10",
+    "git-span-linux-x64": "1.1.10",
+    "git-span-win32-x64": "1.1.10"
   },
   "repository": {
     "type": "git",