Skip to content

docs(release-skill): canary versions must encode their target release #889

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
rickylabs merged 1 commit into from
Jul 18, 2026
Merged

docs(release-skill): canary versions must encode their target release #889

Show file tree
Hide file tree
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
10 changes: 10 additions & 0 deletions .agents/skills/netscript-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,16 @@ prerelease version. For stable target `<next-version>`, the version is `<next-ve
`N` is one greater than the highest matching version found across all workspace-member JSR metadata
(including yanked versions), with existing git tags as a collision guard.

**Canary versioning doctrine (owner decision, 2026-07-18, tracked as #888):** the canary version
must encode the release it is tied to — `<target-version>-canary.N` for the ACTUAL target,
including prereleases: the beta.12 cut publishes `0.0.1-beta.12-canary.1`, and only the real stable
cut publishes `0.0.1-canary.N`. The beta.11 cut published `0.0.1-canary.1` because
`validateStableTarget` in `.llm/tools/release/canary.ts` still refuses prerelease targets — that is
accepted debt for beta.11 only, not a template. When dispatching `release-canary.yml` for a
prerelease cut before #888 lands, the `target-version` input must be the eventual stable version
(the tool derives `<stable>-canary.N` and binds the pair status to the content SHA, which is what
authorizes the prerelease tag); after #888 lands, pass the real prerelease target instead.

The workflow invokes `deno task release:canary -- <next-version>` to perform the shared coordinated
bump/gates and create the ephemeral branch plus provenance tag without a release PR. Operators may
use `--dry-run` in a disposable checkout to rehearse preparation, but must not run a non-dry canary
Expand Down
10 changes: 10 additions & 0 deletions .claude/skills/netscript-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,16 @@ prerelease version. For stable target `<next-version>`, the version is `<next-ve
`N` is one greater than the highest matching version found across all workspace-member JSR metadata
(including yanked versions), with existing git tags as a collision guard.

**Canary versioning doctrine (owner decision, 2026-07-18, tracked as #888):** the canary version
must encode the release it is tied to — `<target-version>-canary.N` for the ACTUAL target,
including prereleases: the beta.12 cut publishes `0.0.1-beta.12-canary.1`, and only the real stable
cut publishes `0.0.1-canary.N`. The beta.11 cut published `0.0.1-canary.1` because
`validateStableTarget` in `.llm/tools/release/canary.ts` still refuses prerelease targets — that is
accepted debt for beta.11 only, not a template. When dispatching `release-canary.yml` for a
prerelease cut before #888 lands, the `target-version` input must be the eventual stable version
(the tool derives `<stable>-canary.N` and binds the pair status to the content SHA, which is what
authorizes the prerelease tag); after #888 lands, pass the real prerelease target instead.

The workflow invokes `deno task release:canary -- <next-version>` to perform the shared coordinated
bump/gates and create the ephemeral branch plus provenance tag without a release PR. Operators may
use `--dry-run` in a disposable checkout to rehearse preparation, but must not run a non-dry canary
Expand Down
Loading