Skip to content

fix: publish packages with trusted OIDC - #132

Merged
willwearing merged 2 commits into
mainfrom
fix/npm-trusted-publishing
Sep 4, 2026
Merged

fix: publish packages with trusted OIDC#132
willwearing merged 2 commits into
mainfrom
fix/npm-trusted-publishing

Conversation

@willwearing

Copy link
Copy Markdown
Owner

Summary

  • publish CLI and MCP packages through npm Trusted Publishing
  • remove the expired token from those publish steps
  • keep executable bin paths intact in npm tarballs

Validation

  • built shared, CLI, and MCP packages with Bun
  • ran npm publish dry runs for CLI 0.2.7 and MCP 0.2.5
  • verified both npm package trusted-publisher connections

@vercel

vercel Bot commented Sep 4, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
graspful Ready Ready Preview Sep 4, 2026 3:09pm UTC

@willwearing
willwearing merged commit 1ee11c7 into main Sep 4, 2026
5 checks passed
@willwearing
willwearing deleted the fix/npm-trusted-publishing branch September 4, 2026 15:18
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