feat(ci): migrate to npm OIDC Trusted Publishing#102
Merged
Conversation
…thin wrapper Required for focus_update + focus_upgrade MCP tools (thin wrapper depends on executeUpgrade exported from @focus-mcp/core 1.2.0).
Add npm upgrade step (npm@latest >= 11.5.1) before each publish step to enable OIDC token-based auth. NODE_AUTH_TOKEN kept as fallback during transition until Trusted Publishers are configured on npmjs.com. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Resolve conflicts: keep OIDC npm upgrade step in workflows, take develop versions for package.json (2.2.0, core ^1.5.0) and CHANGELOG entries. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
npm install -g npm@lateststep before each publish step (enables OIDC support via npm >= 11.5.1)id-token: writeandregistry-urlwere already present — no change needed thereNODE_AUTH_TOKENenv var kept as fallback during transition (can be removed once Trusted Publishers configured on npmjs.com)What changes
.github/workflows/stable-publish.yml.github/workflows/dev-publish.ymlManual action required
Before this PR enables zero-token publishing, configure Trusted Publishers on npmjs.com:
focus-mcp/cli, workflow:stable-publish.ymldev-publish.ymlSee
/home/samuelds/projects/focusmcp/RELEASE_OIDC_SETUP.mdfor full instructions.Rollback
NPM_TOKENsecret is untouched.NODE_AUTH_TOKENfallback remains in workflows.🤖 Generated with Claude Code