Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

docs(ci): the tend environment-deployments gap closed with #3749 (#3764)

Worktrunk Bot2dc9380670cf
diff --git a/.github/CLAUDE.md b/.github/CLAUDE.md
index d85ef3aed..4ff4ef40d 100644
--- a/.github/CLAUDE.md
+++ b/.github/CLAUDE.md
@@ -60,10 +60,11 @@ push to every PR. `deployment: false` drops the record and keeps the gate. The
release jobs keep their records: a tag-push deployment lands in no PR
timeline, and it reads as what it is.
-The generated `tend-*.yaml` files still carry the bare `environment: tend`,
-because they are regenerated by the published `tend` rather than edited here —
-`tend check`'s `environment-deployments` fails until a `uvx tend@latest init`
-regen lands them on tend ≥ 0.1.14.
+The generated `tend-*.yaml` files carry the same `{name: tend, deployment:
+false}`, written by tend's generator rather than edited here — every `uvx
+tend@latest init` overwrites them, so a hand edit would not survive one. tend
+0.1.14 added the field and #3749 landed the regen, which is what cleared `tend
+check`'s `environment-deployments`.
crates.io publishing holds no stored token — it uses Trusted Publishing.
crates.io mints a short-lived one only for an OIDC claim from `release.yaml`