Repository navigation
ci: Publish to npm with trusted publishing - #23
Merged
Merged
Conversation
The NPM_TOKEN secret no longer works, so the v0.8.0 npm publish failed with E404. dbtypr is already configured as an npm trusted publisher for publish.yml, so publish via OIDC instead, matching other seamapi repos: npm-publish@v4, id-token: write, Node 24 (npm >= 11.5.1), no token. Also add a workflow_dispatch trigger that builds an existing tag and publishes it to npm only, to publish v0.8.0 after this merges. Co-Authored-By: Claude Opus 5.5 <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.
Problem: the v0.8.0 npm publish failed with
E404 PUT https://registry.npmjs.org/@seamapi%2fdbtypr. TheNPM_TOKENsecret (last updated 2025-02-28) no longer works.Fix: dbtypr is already configured on npm as a trusted publisher for
publish.yml, so publish via OIDC instead of a token, matching seamapi/types and the other seamapi repos:JS-DevTools/npm-publish@v4,id-token: writeon the npm job, noNPM_TOKENAlso: a
workflow_dispatchtrigger on Publish that builds an existing tag and publishes it to npm only (it skips the GitHub Release and GitHub Packages jobs). This is how v0.8.0 gets to npm after this merges:ci:title, so merging this doesn't cut a release.🤖 Generated with Claude Code