Repository navigation
ci: release to npm with changesets and trusted publishing - #500
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?
Releases
microto npm from GitHub Actions with Changesets and npm Trusted Publishing (OIDC), likevercel/flagsandvercel/serve. There is no npm token, and every release gets a provenance attestation.Today nobody at Vercel can publish
micro: its only npm owner is a former employee, so10.0.2(#497, #498) is tagged but not on npm..github/workflows/release.yml: on push tomain,changesets/actionopens a "Version Packages" PR from pending changesets, or publishes when that PR is merged. Manual runs onmainretry a failed publish..changeset/: Changesets config, with public access and the built-in changelog.package.json: adds@changesets/cli, and replaces the stale lernapublish-*scripts withchangesetandrelease.packages/micro/package.json: expandsrepository. npm requiresrepository.urlto match the GitHub repository exactly when it publishes from GitHub.test/package.json: marks the test workspace as private, sochangeset publishskips it.🤺 How to test?
microadds a Trusted Publisher on npmjs.com: repositoryvercel/micro, workflowrelease.yml. npm requires the first publish within 2 days of that.micro@10.0.2, the version onmainthat is not on npm yet.npm view micro dist-tagsshowslatest: 10.0.2, published by "GitHub Actions" with provenance.Next releases:
pnpm changeset, commit the file, merge, then merge the "Version Packages" PR.🔬 Notes to reviewers
mainonce npm is configured.10.0.2is published frommain, not from tag10.0.2: the code is the same, and only therepositoryfield differs.micro(to10.0.3) and writes itsCHANGELOG.md.🔗 Related PRs
9.xcanary line.