Skip to content

ci(release): Use npm trusted publishing - #2

Merged
iamfj merged 1 commit into
mainfrom
ci/npm-trusted-publishing
Jun 15, 2026
Merged

iamfj merged 1 commit into
mainfrom
ci/npm-trusted-publishing

Conversation

@iamfj

@iamfj iamfj commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • Configure the release workflow for npm Trusted Publishing by removing the long-lived npm token path.
  • Add Node.js 24 setup before semantic-release so npm can use OIDC publishing.
  • Normalize npm package metadata for the repository URL and CLI bin path.
  • Keep package publishing public while relying on GitHub Actions trusted publishing for provenance.

Validation

  • bun run check
  • bun run test
  • bun run pack:dry-run

Security checklist

  • The change doesn't add install-time scripts or unexpected network access.
  • The change doesn't log secrets, tokens, environment values, or raw local state.
  • The change keeps filesystem writes scoped to documented paths.
  • GitHub Actions permissions remain least-privilege.

@vercel

vercel Bot commented Jun 15, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
pi-stack-ops Ready Ready Preview, Comment Jun 15, 2026 3:02pm

@iamfj
iamfj force-pushed the ci/npm-trusted-publishing branch from 63c748f to 01880a6 Compare June 15, 2026 15:01
@iamfj
iamfj marked this pull request as ready for review June 15, 2026 15:02
@iamfj
iamfj merged commit b9b5020 into main Jun 15, 2026
4 checks passed
@iamfj
iamfj deleted the ci/npm-trusted-publishing branch June 15, 2026 15:03
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

This branch was successfully deployed

1 active deployment
Preview — 01880a6c Deployed Jun 15, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant