Compare commits

..
Author SHA1 Message Date
Emeriko 53a834fe6d ci: publish via npm trusted publishing (OIDC), drop NPM_TOKEN
Authenticate the release workflow through GitHub OIDC instead of a long-lived
npm token: no secret to leak or rotate, provenance attached automatically.
Upgrade npm on the runner since OIDC publishing needs npm >= 11.5.1 (Node 22
ships npm 10).
2026-06-24 02:56:32 +02:00
DietrichGebert e368c48c52 feat: scope npm package as @dietrichgebert/ponytail (#280)
Publish under a scope you own outright instead of opencode-ponytail (which
sits on a third-party npm account). Matches the GitHub handle and repo.
publishConfig.access is already public, which scoped public packages need.
2026-06-24 02:50:42 +02:00
+5 -4
View File
@@ -17,7 +17,8 @@ jobs:
- uses: actions/setup-node@v4
with:
node-version: '22'
registry-url: 'https://registry.npmjs.org'
- run: npm publish --provenance --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
# Trusted publishing (OIDC) needs npm >= 11.5.1; Node 22 ships npm 10.
- run: npm install -g npm@latest
# No token: id-token: write above lets npm authenticate via OIDC, and
# provenance is attached automatically. access set in publishConfig.
- run: npm publish