docs(release): a failed canary is fixed forward, not yanked - #1055
Merged
Conversation
Owner decision, 2026-08-02: a canary that published and then failed its pinned production E2E is fixed forward with the next canary.N, without yanking the failed version. A canary is a prerelease that normal semver resolution never selects, so a failed one is inert for consumers and is useful audit evidence. Yanking remains available for a canary that is actively harmful to resolve, as an owner judgement call rather than the default response to a red gate. Recorded after 0.0.3-canary.1 published and scaffold.plugin.ai.lifecycle failed in run 30739345727.
This was referenced Aug 2, 2026
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
1 participant
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.
Summary
Records the owner's 2026-08-02 decision on failed canaries: a canary that published and then failed
its pinned production E2E is fixed forward with the next
canary.N, without yanking the failed one.The skill previously mandated yanking in that case. Practice diverged from it during the 0.0.3 cut,
so this aligns the doctrine rather than leaving the two silently inconsistent.
Rationale
A canary is a prerelease. Normal semver resolution never selects it, so a failed canary is inert for
consumers and remains useful as audit evidence of what was attempted. Yanking added ceremony and risk
without changing what anyone resolves.
Yanking stays documented for the case it was actually written for — a canary that is harmful to
resolve, such as one that published corrupt or wrong-identity artifacts. That is now framed as an
owner judgement call rather than the default response to any red gate.
The stable channel is unaffected either way:
release/canary-pairis written only on a green pair,and
release:publishfails closed without it.Context
0.0.3-canary.1published across the workspace, thenscaffold.plugin.ai.lifecyclefailed inrun 30739345727. The underlying
defect is tracked in #1054. Under the previous wording that would have required yanking 9+ published
packages; under this wording the next canary simply supersedes it.
Docs-only change to
.agents/skills/netscript-release/SKILL.md. No tooling or workflow behaviour isaltered — nothing in the release path reads this file.