@codacy/verity-cli 0.35.3-experimental.f980d82 → 0.35.4

package/CHANGELOG.md

@@ -64,6 +64,74 @@ installs are untouched.
   which is the ordinary case for someone whose first Verity install *is* the
   plugin.
 
+## [0.35.4] — 2026-11-10
+
+### 📐 The Standard file is machine-local
+
+- **`.verity/standard.yaml` is no longer committed.** Reviews read the Standard
+  on the Verity service, and the service copy moves without the file (`verity
+  standard generate` on another machine, the catalogue conversion, a suggestion
+  accepted on the dashboard), so the committed copy was routinely stale. The
+  file is now this machine's working copy: `verity init` and `verity standard
+  pull` write it from the service, and the `.gitignore` block `verity init`
+  writes ignores it. A project whose file is already tracked is not converted:
+  `verity init` and `verity doctor` say so and name `verity standard untrack`,
+  which stages the removal (the file stays on disk). Teammates get the file
+  back with `verity standard pull`. `.verityignore` and `VERITY.md` stay
+  committed.
+- **`verity standard push` is conditional.** It sends the version this machine
+  last pulled, adopted, pushed or matched, and the service writes the next
+  version only when that is still the latest. Otherwise nothing is written, and
+  the message names `verity standard pull` (pull, re-apply your changes, push
+  again) and `--force`, which keeps the old unconditional push. A machine with
+  no record reads the latest first and expects exactly that.
+- **`verity init` with a Standard file here compares it with the team's.** The
+  same Standard: kept, and named as that version. None on the service: shared.
+  A different one: init asks (Enter uses the team's, `k` keeps yours), and an
+  unattended run uses the team's; your file is kept as
+  `.verity/standard.<time>.yaml`. `--standard use` is honoured here now. Before,
+  the file was kept without a look at the team's, so a teammate on a cloned
+  repository was never told it differed, and a push of it replaced the team's.
+- **`verity doctor`** reports a tracked Standard file, and a missing file is no
+  longer "run `synthesize --push`" (which would replace the team's Standard
+  with a derived one from a clone): it is `verity standard pull` when this
+  machine knows the team's version, and `verity init` otherwise.
+- **The one-time knowledge seed** reads the Standard on the service when there is
+  no file here, so a checkout without the file seeds its graph too.
+
+### 🌐 The service has a domain
+
+- **The Verity service is `https://server.verity.md`.** A new login, and every
+  credential and VERITY.md that names the old `ofcamwrjwrkazqvdchko.supabase.co`
+  address, uses it. Nothing to do: the old address names the same service and
+  keeps working, and a login made against one address is accepted at the other.
+
+## [0.35.3] — 2026-11-05
+
+### 🔧 Fixes
+
+- **`verity init` on a repository the Verity GitHub App cannot see gives it
+  access in the same run.** Init offers a GitHub sign-in that opens the page
+  where you add the repository to the Verity app, waits for it, and then
+  continues. Init says why a second sign-in is needed: Verity reads your
+  repository access from GitHub only when you sign in. With `--yes` or no
+  terminal, init names the one action instead.
+- **Init states a refusal as a refusal.** When the service refuses access to
+  the repository, init writes nothing, says that Verity cannot access the
+  repository yet, names the one action, and exits 1. Before, it said the
+  service did not answer and told you to run `verity init` again.
+- **A turn with nothing new to review no longer prints a Verity line.**
+  Before, a line such as "No files modified since last analysis" showed under
+  every message. `verity config verbose on` brings the line back. Turns that
+  wrote code still get their review, and a change that nobody reviewed is
+  still reported.
+- **The upgrade link in a plan-limit message is clickable.** It keeps its
+  `https://`.
+- **`verity usage` says "your plan" for the plan you own, and `verity status`
+  no longer lists that plan under "member of".** A team you belong to is still
+  listed as a team.
+- Includes security fixes.
+
 ## [0.35.2] — 2026-10-30
 
 ### 🔧 Fixes