Repository navigation
ci: set up automated releases with Changesets - #3
Merged
Merged
Conversation
Add Changesets config, release scripts, and a Release Packages workflow that opens a version PR and publishes to npm with OIDC provenance on merge to main.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
…ents - Rename release-packages.yml -> release.yml to match the workflow filename the npm trusted publisher is configured to trust; OIDC validates the exact filename. - Bump Node to 24 and upgrade npm to latest, since npm OIDC trusted publishing requires npm >= 11.5.1 (Node 22 bundles npm 10.x).
quuu
approved these changes
Jul 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
2 participants
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.
Summary
Sets up automated, reviewable releases using Changesets, following the pattern in
vercel/repository-dispatch, adapted for this single package and for npm OIDC trusted publishing..changeset/config.json— Changesets config (public access,mainbase branch).package.json— addschangeset,version-packages, andrelease(pnpm build && changeset publish) scripts; adds@changesets/cli; pinspackageManagertopnpm@10.9.0..github/workflows/release.yml— on push tomain,changesets/actionopens/updates a "Version Packages" PR or, when that merges, publishes to npm. Publishes via OIDC trusted publishing (id-token: write) — no npm token.npm OIDC requirements (met in this PR)
release.yml— must exactly match the workflow the npm trusted publisher is configured to trust (OIDC validates the filename).npm install -g npm@latest— npm trusted publishing requires npm ≥ 11.5.1 and Node ≥ 22.14; Node 22 ships npm 10.x, so we upgrade explicitly.Prerequisites (owner action, outside this PR)
vercel/detect-agent→release.yml(done by the package owner).GH_TOKEN_PULL_REQUESTS— a PAT / GitHub App token withcontents:write+pull-requests:write, so the version PR can be opened and trigger CI. Still required.Verification
pnpm install --frozen-lockfile,lint,format:check,test(68),buildall pass.pnpm version-packages: bumped1.0.0 → 1.0.1and wroteCHANGELOG.md, then reverted.main.🤖 Generated with Claude Code