fix: configure npm trusted publishing for semantic-release #3
Conversation
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
- Add comprehensive comments explaining npm trusted publishing setup - Include references to npm and semantic-release documentation - Document OIDC requirements and provenance generation - Clarify the security benefits of trusted publishing over token-based auth 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
natedanner
approved these changes
Sep 23, 2025
- Remove @semantic-release/npm plugin to avoid NPM_TOKEN requirement - Add manual npm publish step with --provenance flag for trusted publishing - Keep semantic-release for versioning, changelog, git tags, and GitHub releases - Use npm pack to create tarball for GitHub release assets - Maintains all automation while enabling OIDC-based npm authentication This approach leverages npm's native trusted publishing support while preserving semantic-release's version management and release automation. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
github-actions bot
pushed a commit
that referenced
this pull request
Sep 23, 2025
# [4.1.0](v4.0.0...v4.1.0) (2025-09-23) ### Bug Fixes * add contents write permission to publish workflow ([#2](#2)) ([c9183f6](c9183f6)) * configure npm trusted publishing for semantic-release ([#3](#3)) ([2db52a7](2db52a7)) ### Features * configure npm trusted publishing support ([a33b2e7](a33b2e7))
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
Changes
Workflow Updates (
.github/workflows/publish.yaml)contents: writepermission for creating releases and pushing tagsregistry-urlconfiguration for npm registry setupNPM_CONFIG_PROVENANCE: trueto enable provenance generationSemantic Release Updates (
.releaserc.yaml)npmPublish: trueto explicitly enable npm publishingprovenance: trueto enable npm provenance for trusted publishingBenefits
NPM_TOKENsecret managementReferences
Test plan
🤖 Generated with Claude Code