Skip to content

ci(release): publish to npm through trusted publishing - #46

Merged
systemfsoftware-bot merged 1 commit into
mainfrom
ci/npm-trusted-publishing
Nov 15, 2026
Merged

systemfsoftware-bot merged 1 commit into
mainfrom
ci/npm-trusted-publishing

Conversation

@systemfsoftware-bot

Copy link
Copy Markdown
Contributor

Turns on npm-publish in the shared release workflow (pnpm-release-management 9615867c17) and grants id-token: write. On each push to main, a GitHub-hosted job uploads every version of this repository's packages that npm lacks, through trusted publishing with provenance and no token, then waits until all of them install. discern proved the setup: 1.1.4 is on npm, published by GitHub Actions with SLSA provenance.

The release workflow publishes every version npm lacks from a GitHub-hosted
job with an OIDC identity; no npm token exists.
@systemfsoftware-bot
systemfsoftware-bot merged commit a224b2e into main Nov 15, 2026
4 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