docs(ci): the tend environment-deployments gap closed with #3749 - #3764
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nightly sweep finding: the last paragraph of "Environment protection" in
.github/CLAUDE.mddescribes a gap that closed the same night it was written.#3748 added the paragraph saying the generated
tend-*.yamlfiles "still carry the bareenvironment: tend" and thattend check'senvironment-deployments"fails until auvx tend@latest initregen lands them on tend ≥ 0.1.14". #3749 merged 3 hours later and did exactly that regen — every generated job now reads{name: tend, deployment: false}, and tonight'stend checkreportsenvironment-deploymentsasPASS. Left as-is, the file tells the next reader to expect a failure that no longer happens and a regen that already ran.The rewrite keeps the durable half — the generated files aren't hand-edited, because
uvx tend@latest initoverwrites them — and states the resolution instead of the pending action.Evidence
Current state of the generated files (all eight are identical in shape):
Tonight's
tend check, run by the nightly sweep:The three checks still failing (
credential-environments,claude-auth,repo-secret-allowlist) are tracked in #3729 and are repository-settings changes, unrelated to this file. #3760 edits the same section but not these lines, so the two don't conflict.No test accompanies this — it's a documentation-only change to a file no test reads.