@codacy/verity-cli 0.33.1-experimental.4a41d04 → 0.33.2-experimental.0c53bed

package/CHANGELOG.md

@@ -64,6 +64,29 @@ installs are untouched.
   which is the ordinary case for someone whose first Verity install *is* the
   plugin.
 
+## [0.33.2] — 2026-09-23
+
+**Which build is gating, said out loud.**
+
+- **`verity doctor` and `verity hooks check` now say which build is gating.**
+  Both print the plugin's version and the CLI its hooks actually load, and warn
+  when the `verity` in your terminal is not that CLI. A mismatch never announced
+  itself as a version number before — it showed up as a command that seemed to
+  do nothing, because the gate and the terminal were running different builds.
+  The remedy names the side that is behind: `npm install -g @codacy/verity-cli@…`
+  for a stale global, `claude plugin update verity@verity` for a stale plugin.
+- **The stale-CLI warning no longer fires on installs that are fine.** It
+  compared your global `verity` against the plugin's *manifest* version, which
+  is not what the plugin runs — so a plugin whose manifest and pinned CLI differ
+  produced a warning telling you to install a version the hooks never use. The
+  comparison is now against the CLI the resolver actually loads.
+- **The READMEs give an update command that exists.** From your shell,
+  `claude plugin update verity@verity`, then `/reload-plugins` in any open
+  session — there is no `/plugin update` slash command. Removing the plugin is
+  documented beside it: `claude plugin uninstall verity@verity -s user`, or
+  `-s project` / `-s local` for the scope you installed at, since each scope is a
+  separate install.
+
 ## [0.33.1] — 2026-09-18
 
 **The timed agent review runs for everyone.**