Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
max-sixty merged 1 commit into from
Aug 7, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions .github/CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,10 +59,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`
Expand Down
Loading