canary

# Find Or Publish Canary Release Use this skill to get a branch-specific canary build from `pkg.pr.new`. Canary publishes are driven by the `publish-canary.yml` workflow. Automatic canary publishes: - Every push to `next` - In-repo PRs labeled `ci:canary` (a human must apply that label). While it remains, every push to the PR republishes. The label does nothing on fork PRs. ## Version string The canary version string is constructed like this: ```text storybook@https://pkg.pr.new/storybook@<SHA> ``` Replace `<SHA>` with the short commit SHA (first 7 characters). Compact URLs (`https://pkg.pr.new/storybook@<SHA>`) resolve to the same tarball as the owner/repo form. The pkg.pr.new dashboard is always `https://pkg.pr.new/~/storybookjs/storybook`. ## Check whether a canary already exists ```bash SHA=$(git rev-parse --short=7 HEAD) curl -I "https://pkg.pr.new/storybook@$SHA" ``` An HTTP `200` status code means the canary already exists for that commit. ## Decision flow Use this skill with the following if-then behavior. ### A. If the branch already has a PR with the `ci:canary` label Do not trigger anything manually. Read the canary heading and install commands from the PR body. That section is the current run status and the most recent release. ```bash BRANCH=$(git branch --show-current) gh pr list \ --repo storybookjs/storybook \ --head "$BRANCH" \ --state open \ --json number,title,labels,url \ --jq '.[] | select(any(.labels[]?; .name == "ci:canary"))' ``` ...