Repository navigation
ci: publish canary versions with trusted publishing - #501
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
AndyBitz
approved these changes
Nov 9, 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
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.
🖖 What's in there?
Lets the
9.xline publish canary versions to npm from GitHub Actions with npm Trusted Publishing (OIDC). There is no npm token, and every release gets a provenance attestation. This unblocksmicro@9.3.5-canary.4(#496, #499), which is tagged but not on npm..github/workflows/release.yml: a manual workflow. On9.x, it publishes the current version under thecanarydist-tag. It refuses versions without-canary.and skips versions already on npm.packages/micro/package.json: replaceszeit/microwith the fullrepositoryofvercel/micro. npm requiresrepository.urlto match the GitHub repository exactly.🤺 How to test?
vercel/micro, workflowrelease.yml).9.x:npm view micro dist-tagsshowscanary: 9.3.5-canary.4, andlatestis unchanged.🔬 Notes to reviewers
9.x: this 2019 Yarn branch only gets occasional canaries, and a version-bump PR plus a manual run is enough.release.yml, like onmain: npm binds the Trusted Publisher to one file name.npm publish --dry-run:9.3.5-canary.4publishes with tagcanary,9.3.5-canary.3is skipped as already published, and9.3.4is refused.🔗 Related PRs
main.