Skip to content

fix(release): use npm publish for OIDC trusted-publisher auth#85

Merged
ctate merged 1 commit intomainfrom
fix/release-npm-publish
Apr 29, 2026
Merged

fix(release): use npm publish for OIDC trusted-publisher auth#85
ctate merged 1 commit intomainfrom
fix/release-npm-publish

Conversation

@ctate
Copy link
Copy Markdown
Collaborator

@ctate ctate commented Apr 29, 2026

Summary

  • Switch from pnpm publish --provenance to npm publish --provenance so OIDC trusted-publisher auth works
  • Drop pinned pnpm version in the workflow
  • All workspace:* references are in devDependencies only, so npm publish works without resolution

The v0.5.0 Release workflow failed because pnpm publish does not pass the OIDC token needed for npm trusted publishers. This matches the working pattern in wterm.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Apr 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
emulate Ready Ready Preview, Comment Apr 29, 2026 5:33am

Comment thread .github/workflows/release.yml Outdated
pnpm publish does not pass the OIDC token needed for npm trusted
publishers, causing 404 errors on every package. Switch to pnpm pack
(to resolve workspace:* protocols) followed by npm publish (which
supports OIDC auth via --provenance).
@ctate ctate force-pushed the fix/release-npm-publish branch from 88ebc5a to 02b9c57 Compare April 29, 2026 05:32
@ctate ctate merged commit f3a26ff into main Apr 29, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant