@codacy/verity-cli 0.33.0 → 0.33.1-experimental.1378de3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +25 -0
- package/bin/verity.js +702 -557
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -38,6 +38,18 @@ installs are untouched.
|
|
|
38
38
|
|
|
39
39
|
### 🔧 Plugin fixes
|
|
40
40
|
|
|
41
|
+
- **`verity doctor` and `verity hooks check` now say which build is gating.**
|
|
42
|
+
Both print the plugin's version and the CLI its hooks actually load, and warn
|
|
43
|
+
when the `verity` in your terminal is not that CLI. A mismatch never announced
|
|
44
|
+
itself as a version number before — it showed up as a command that seemed to
|
|
45
|
+
do nothing, because the gate and the terminal were running different builds.
|
|
46
|
+
The remedy names the side that is behind: `npm install -g @codacy/verity-cli@…`
|
|
47
|
+
for a stale global, `claude plugin update verity@verity` for a stale plugin.
|
|
48
|
+
- **The stale-CLI warning no longer fires on installs that are fine.** It
|
|
49
|
+
compared your global `verity` against the plugin's *manifest* version, which
|
|
50
|
+
is not what the plugin runs — so a plugin whose manifest and pinned CLI differ
|
|
51
|
+
produced a warning telling you to install a version the hooks never use. The
|
|
52
|
+
comparison is now against the CLI the resolver actually loads.
|
|
41
53
|
- **Uninstalling the plugin left projects with no gate at all.** Whether the
|
|
42
54
|
plugin owned a project's hooks was decided by whether its install directory
|
|
43
55
|
existed on disk — and that directory survives an uninstall. Every project the
|
|
@@ -64,6 +76,19 @@ installs are untouched.
|
|
|
64
76
|
which is the ordinary case for someone whose first Verity install *is* the
|
|
65
77
|
plugin.
|
|
66
78
|
|
|
79
|
+
## [0.33.1] — 2026-09-18
|
|
80
|
+
|
|
81
|
+
**The timed agent review runs for everyone.**
|
|
82
|
+
|
|
83
|
+
- **On at every commit and push, with nothing to switch on.** The second reviewer
|
|
84
|
+
that arrived in 0.33.0 was opt-in, and no project ever opted in — it shipped and
|
|
85
|
+
never ran once. It now runs by default at both git moments: it reads the code
|
|
86
|
+
the one-shot only saw as a diff, checks what that review claimed, and can clear,
|
|
87
|
+
downgrade or add findings. `process_constraints.git_moment_agent: off` opts a
|
|
88
|
+
project out and `push` limits it to pushes; `VERITY_GIT_MOMENT_AGENT=off` skips
|
|
89
|
+
it on one machine. Only the exact value `off` turns it off — a misspelling
|
|
90
|
+
leaves the review running.
|
|
91
|
+
|
|
67
92
|
## [0.33.0] — 2026-09-16
|
|
68
93
|
|
|
69
94
|
**Knowledge that holds across your organization's repositories now reaches every
|