@codacy/verity-cli 0.35.1-experimental.19ce23f → 0.35.2

package/CHANGELOG.md

@@ -64,15 +64,41 @@ installs are untouched.
   which is the ordinary case for someone whose first Verity install *is* the
   plugin.
 
+## [0.35.2] — 2026-10-30
+
+### 🔧 Fixes
+
+- **`verity init --standard new` works when `.verity/standard.yaml` already
+  exists.** Init sets your file aside (a copy goes to
+  `.verity/standard.<time>.yaml`) and builds a new Standard with review packs
+  and, if you send the repository profile, project rules. Before, init kept
+  the old file and ignored the flag.
+- **A kept Standard that does not use review packs says how to move it:**
+  `verity standard push` keeps your rules, and `verity init --standard new`
+  starts over.
+- **A copy of your Standard never replaces an earlier copy.** `verity init
+  --standard new` and `verity standard pull` create the copy as a new file.
+  If a copy with the same time exists, the new copy gets the next name
+  (`standard.<time>-1.yaml`).
+
+## [0.35.1] — 2026-10-30
+
+### 📐 Standards
+
+- **`verity standard catalogue`** lists every review pack and what it holds.
+  `verity standard catalogue <pack>` shows the rules of one pack, with their
+  rule text. The packs your Standard extends are marked. The same catalogue
+  is at [verity.md/review-packs](https://verity.md/review-packs).
+
 ## [0.35.0] — 2026-10-30
 
 **A new first run: sign in, answer two questions, and work with your team's Standard.**
 
 ### 🚀 `verity init`
 
-- **Sign-in comes first.** Then init asks two questions: when Verity reviews
-  (each turn, each commit, each push; all three by default), and, when the
-  service writes project rules for you, whether to send a profile of the
+- **Sign-in comes first.** Verity reviews each turn, each commit and each
+  push by default (`verity config moments` changes it). When the service
+  writes project rules for you, init asks whether to send a profile of the
   repository for them.
 - **Your team's Standard.** When the service has one, init offers it, or a new
   one (`--standard use|new`). It never pushes a Standard over a team's Standard