ci: route every release through Production, drop the canary path - #27
Merged
Conversation
npm allows one trusted publisher per package with one optional environment claim, so publishing from two environments meant the publisher could not be pinned to either. Pin it to Production instead and run every tag there. The canary path was the only thing forcing the split, and it was never used: zero workflow_dispatch runs of release.yml, no 0.0.0-<sha> version and no `canary` dist-tag ever published. Removing it collapses the environment expression to a constant. Beyond the npm pin, this makes the rc a faithful rehearsal. Prereleases used to run in Development, so a green rc exercised a credential path the stable release never took — v5.1.0-rc.1 passed on 2026-07-23 and v5.1.0 then failed to publish on 2026-08-04. Same environment now means a green rc predicts the release. The cost is one approval click per rc; Production has prevent_self_review: false, so the releaser can approve their own run. Update the release skill to match: the environment pin is now a documented precondition on both sides, the pre-tag guard asserts release.yml still carries it, and E404-on-PUT is written up as an auth failure rather than a missing-package one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Benchmark Comparison
Contract: escrow
Contract: logic
Contract: multitoken
Contract: nft
Contract: token
Contract: vault
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
.