@codacy/verity-cli 0.33.0-experimental.d60f544 → 0.33.1-experimental.4a41d04
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 +29 -0
- package/bin/verity.js +851 -667
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -64,6 +64,19 @@ installs are untouched.
|
|
|
64
64
|
which is the ordinary case for someone whose first Verity install *is* the
|
|
65
65
|
plugin.
|
|
66
66
|
|
|
67
|
+
## [0.33.1] — 2026-09-18
|
|
68
|
+
|
|
69
|
+
**The timed agent review runs for everyone.**
|
|
70
|
+
|
|
71
|
+
- **On at every commit and push, with nothing to switch on.** The second reviewer
|
|
72
|
+
that arrived in 0.33.0 was opt-in, and no project ever opted in — it shipped and
|
|
73
|
+
never ran once. It now runs by default at both git moments: it reads the code
|
|
74
|
+
the one-shot only saw as a diff, checks what that review claimed, and can clear,
|
|
75
|
+
downgrade or add findings. `process_constraints.git_moment_agent: off` opts a
|
|
76
|
+
project out and `push` limits it to pushes; `VERITY_GIT_MOMENT_AGENT=off` skips
|
|
77
|
+
it on one machine. Only the exact value `off` turns it off — a misspelling
|
|
78
|
+
leaves the review running.
|
|
79
|
+
|
|
67
80
|
## [0.33.0] — 2026-09-16
|
|
68
81
|
|
|
69
82
|
**Knowledge that holds across your organization's repositories now reaches every
|
|
@@ -107,6 +120,22 @@ repository — the reviewer, the agent, and you.**
|
|
|
107
120
|
ask. It is stored as `source: agent` — Verity thought this, nobody checked it —
|
|
108
121
|
and `--confirmed` marks the words a person authored.
|
|
109
122
|
|
|
123
|
+
## [0.32.7] — 2026-09-16
|
|
124
|
+
|
|
125
|
+
**Static analysis works on Windows.**
|
|
126
|
+
|
|
127
|
+
- **`@codacy/analysis-cli` is found on Windows.** Verity looked for it by running
|
|
128
|
+
`which`, which does not exist in `cmd.exe`. Every Windows machine therefore
|
|
129
|
+
reported the analyzer missing even when it was installed and working: static
|
|
130
|
+
analysis was silently skipped, and `verity init` fell back to documented Trivy
|
|
131
|
+
pattern ids instead of deriving them from your project. Binaries are now found
|
|
132
|
+
by walking `PATH` with `PATHEXT`, which also picks up the `.cmd` shims npm
|
|
133
|
+
installs. The same broken probe was used for `claude` and for `verity` itself.
|
|
134
|
+
- **A missing analyzer is no longer reported as a clean scan.** When
|
|
135
|
+
`@codacy/analysis-cli` was not installed, Verity sent an empty result that
|
|
136
|
+
looked identical to a scan that ran and found nothing. It now says the analyzer
|
|
137
|
+
did not run. No gate decision changes as a result of this.
|
|
138
|
+
|
|
110
139
|
## [0.32.6] — 2026-09-14
|
|
111
140
|
|
|
112
141
|
**The knowledge base is no longer committed to git.**
|