From 4d5e9255a2bf0e3857f075f29d09806d90289f36 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 8 Sep 2026 04:00:13 +0000 Subject: [PATCH] docs: correct false "plugin manager detects updates" versioning rationale MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit feedBack core's own CLAUDE.md is explicit that the plugin loader does not consume a plugin's manifest version for update detection — it's only used as a cache-busting query param on served JS/CSS URLs. This repo's Versioning section repeated the inaccurate "the plugin manager uses this to detect updates" claim; replaced with the real rationale (feedback core issue #70). Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_016cfE1wg6F2VT6eqJEp4LBz --- CLAUDE.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 7fe826b..328f460 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -53,6 +53,8 @@ reading state straight off the Host's `window.highway` object. Bump `version` in `plugin.json` whenever a change is user-visible — a rendering fix, a new interaction (click/wheel/hover), a changed setting -(best-practices rule 4: bump on every release; the plugin manager uses -this to detect updates). Patch (`1.x.y`) for fixes, minor (`1.x.0`) for -new features, matching normal semver conventions. +(best-practices rule 4: bump on every release — the version is used for +cache-busting the served JS/CSS URL, so an unbumped version means users +keep getting stale cached files after an update). Patch (`1.x.y`) for +fixes, minor (`1.x.0`) for new features, matching normal semver +conventions.