@codacy/verity-cli 0.32.6 → 0.32.7
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 +16 -0
- package/bin/verity.js +653 -605
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -64,6 +64,22 @@ 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.32.7] — 2026-09-16
|
|
68
|
+
|
|
69
|
+
**Static analysis works on Windows.**
|
|
70
|
+
|
|
71
|
+
- **`@codacy/analysis-cli` is found on Windows.** Verity looked for it by running
|
|
72
|
+
`which`, which does not exist in `cmd.exe`. Every Windows machine therefore
|
|
73
|
+
reported the analyzer missing even when it was installed and working: static
|
|
74
|
+
analysis was silently skipped, and `verity init` fell back to documented Trivy
|
|
75
|
+
pattern ids instead of deriving them from your project. Binaries are now found
|
|
76
|
+
by walking `PATH` with `PATHEXT`, which also picks up the `.cmd` shims npm
|
|
77
|
+
installs. The same broken probe was used for `claude` and for `verity` itself.
|
|
78
|
+
- **A missing analyzer is no longer reported as a clean scan.** When
|
|
79
|
+
`@codacy/analysis-cli` was not installed, Verity sent an empty result that
|
|
80
|
+
looked identical to a scan that ran and found nothing. It now says the analyzer
|
|
81
|
+
did not run. No gate decision changes as a result of this.
|
|
82
|
+
|
|
67
83
|
## [0.32.6] — 2026-09-14
|
|
68
84
|
|
|
69
85
|
**The knowledge base is no longer committed to git.**
|