@codacy/verity-cli 0.33.2 → 0.33.3-experimental.072d5cb
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 +26 -0
- package/bin/verity.js +1315 -732
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -64,6 +64,32 @@ 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.3] — 2026-09-24
|
|
68
|
+
|
|
69
|
+
**The knowledge seed runs once per project, not once per checkout.**
|
|
70
|
+
|
|
71
|
+
- **`verity memory seed` and the analyze auto-seed no longer re-seed a project
|
|
72
|
+
that is already seeded.** The old "already seeded" check looked for a file the
|
|
73
|
+
server never writes (`domain/project-overview.md`; nodes are named
|
|
74
|
+
`n{seq}-{slug}.md`), so it never matched, and an empty, not-yet-pulled
|
|
75
|
+
`.verity/memory/` in a fresh clone or worktree read as "never seeded". Every
|
|
76
|
+
new checkout posted the whole batch again and the server recorded every copy.
|
|
77
|
+
One project reached 13,497 nodes, 11,214 of them copies of 38 seed titles, and
|
|
78
|
+
every analyze for it died on request size (HTTP 546, VRT-243). The CLI now
|
|
79
|
+
checks the frontmatter of what is on disk, then asks the server which seed
|
|
80
|
+
titles the project has, and posts only the titles that are missing — so a
|
|
81
|
+
seed that only half landed is completed, and a seeded project is never
|
|
82
|
+
re-posted.
|
|
83
|
+
- **The server refuses to record the same seed twice.** Posting a seed node whose
|
|
84
|
+
title and body the project already carries returns the existing node
|
|
85
|
+
(`200`, `deduplicated: true`) instead of minting another. This holds for old
|
|
86
|
+
CLIs, cleared markers and parallel worktrees alike. A seed whose body changed
|
|
87
|
+
(the README was edited) is still a new node, and an archived seed can be
|
|
88
|
+
recorded again.
|
|
89
|
+
- `verity memory seed` reports nodes that already existed apart from nodes it
|
|
90
|
+
created, and `--force` re-materializes the existing nodes locally rather than
|
|
91
|
+
duplicating them.
|
|
92
|
+
|
|
67
93
|
## [0.33.2] — 2026-09-23
|
|
68
94
|
|
|
69
95
|
**Which build is gating, said out loud.**
|