Commit c910c58
authored
ci: re-enable npm provenance now that the repo is public (#35)
Closes #4.
One line: `npm publish --access public` → `npm publish --access public
--provenance`.
The flag was removed while the repo was internal, since npm provenance
requires a public repository. That's no longer true, so published
packages can carry [sigstore provenance
attestations](https://docs.npmjs.com/generating-provenance-statements)
again — npmjs.com shows a "Built and signed on GitHub Actions" badge
linking back to the workflow run that produced the tarball.
## Prerequisites, verified against the workflow
- `id-token: write` is already granted at workflow level (alongside
`contents: write`) — provenance needs it to mint the OIDC token.
- The job already runs `npm install -g npm@latest` before publishing, so
the npm version is new enough to support the flag.
- `actions/setup-node` already sets `registry-url`.
Nothing else changes. `NODE_AUTH_TOKEN` and the tag-vs-`package.json`
version check are untouched.
## Note on verification
This can only be confirmed by cutting a release — there's no way to
exercise `npm publish` from CI without publishing. The next tagged
release will either produce a package with provenance or fail loudly at
the publish step, which is the same blast radius the publish step
already has.
Complementary to #21: sigstore provenance proves who built the npm
package; Kosli attestations record what the artifact is and what
evidence backs it.1 parent b9cc543 commit c910c58
1 file changed
Lines changed: 5 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
51 | | - | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
52 | 56 | | |
53 | 57 | | |
54 | 58 | | |
| |||
0 commit comments