@macintacos/caret 0.12.0 → 0.14.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "caret",
-  "version": "0.12.0",
+  "version": "0.14.0",
   "description": "Review, annotate, and approve Claude Code plans in a local web UI.",
   "author": { "name": "macintacos" },
   "homepage": "https://github.com/macintacos/caret",

package/README.md

@@ -69,6 +69,19 @@ agent applies an update. In OpenCode, caret toasts you at startup when a newer r
 out; a plain `install` at a terminal runs its own check against npm and asks before taking
 it.
 
+caret's daemon runs the same check for itself, at most once a day. The call is
+unauthenticated and sends nothing about you — just a request to npm or GitHub, depending
+on how caret was installed, for the newest published version. When a newer caret is out,
+the review UI says so once: a toast on load, a mark on the settings button, and a
+**Settings → Updates** pane naming the version and the exact command to take it.
+
+Turn the check off from that same pane, or by setting `updates.check` to `false` in
+`prefs.json` (`~/.local/state/caret/prefs.json`, or under `$XDG_STATE_HOME/caret`):
+
+```json
+{ "updates": { "check": false } }
+```
+
 See [the OpenCode adapter](doc/ARCHITECTURE.md#the-opencode-adapter) for the by-hand
 equivalents, for pinning a version in OpenCode's `plugin` array, and for what each agent's
 install touches; [the Claude Code adapter](doc/ARCHITECTURE.md#the-claude-code-adapter)