Repository navigation
Publish to npm with trusted publishing (OIDC) - #79
Merged
Merged
Conversation
Release runs failed with E404 on PUT because no valid NPM_TOKEN was available. Switch the release workflow to npm trusted publishing: grant id-token: write, publish with Node 24 (npm >= 11.5.1), and enable provenance. The NPM_TOKEN secret is no longer used. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWMeBqmYDKGbGuJ23fJ
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.
Requested by Ryan · project thread
Why
The Release run for #78 (run) failed: changesets logged
No NPM_TOKEN or OIDC availableandnpm publishgotE404 Not Found - PUT .../@solidjs%2fmeta. So 0.29.8 never reached npm (latestis still 0.29.4).What
Same setup as solid-router / vite-plugin-solid:
permissions: id-token: write(pluscontents/pull-requests: writefor the changesets PR)NPM_CONFIG_PROVENANCE: 'true';NPM_TOKENis no longer passedpackage.jsonrepository.urlis alreadyhttps://github.com/solidjs/solid-meta, which matches the repo, so provenance will validate.Before merging
A trusted publisher must be added for
@solidjs/metaon npmjs.com (Settings → Trusted publishing → GitHub Actions): orgsolidjs, reposolid-meta, workflowrelease.yml, environment empty. Merging this then re-runs Release, which publishes 0.29.8.Generated by Claude Code