@codacy/verity-cli 0.35.0 → 0.35.1

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.
Files changed (3) hide show
  1. package/CHANGELOG.md +12 -3
  2. package/bin/verity.js +728 -559
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -64,15 +64,24 @@ 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.35.1] — 2026-10-30
68
+
69
+ ### 📐 Standards
70
+
71
+ - **`verity standard catalogue`** lists every review pack and what it holds.
72
+ `verity standard catalogue <pack>` shows the rules of one pack, with their
73
+ rule text. The packs your Standard extends are marked. The same catalogue
74
+ is at [verity.md/review-packs](https://verity.md/review-packs).
75
+
67
76
  ## [0.35.0] — 2026-10-30
68
77
 
69
78
  **A new first run: sign in, answer two questions, and work with your team's Standard.**
70
79
 
71
80
  ### 🚀 `verity init`
72
81
 
73
- - **Sign-in comes first.** Then init asks two questions: when Verity reviews
74
- (each turn, each commit, each push; all three by default), and, when the
75
- service writes project rules for you, whether to send a profile of the
82
+ - **Sign-in comes first.** Verity reviews each turn, each commit and each
83
+ push by default (`verity config moments` changes it). When the service
84
+ writes project rules for you, init asks whether to send a profile of the
76
85
  repository for them.
77
86
  - **Your team's Standard.** When the service has one, init offers it, or a new
78
87
  one (`--standard use|new`). It never pushes a Standard over a team's Standard