Publish releases from CI via OIDC trusted publishing - #132
Merged
Conversation
Tag-triggered workflow publishes to npm (trusted publishing, no tokens in CI) and the MCP registry (GitHub Actions OIDC). The tag must match package.json, the full suite runs first, and each publish step skips a registry that already carries the version so a partially-shipped release can be completed with a manual re-run. CONTRIBUTING documents the flow. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Tag-triggered
releaseworkflow: verifies the tag matches release metadata, runs the full suite, then publishes to npm via OIDC trusted publishing and to the MCP registry via GitHub Actions OIDC. No tokens exist in CI; each publish step skips a registry that already carries the version, so a partial release can be completed with a manual re-run. CONTRIBUTING gains the release runbook.Requires one-time npm configuration: package settings, Publishing access, Trusted Publisher (GitHub Actions, repository wkoverfield/quilt, workflow release.yml).
🤖 Generated with Claude Code