Skip to content

feat: add npm provenance attestation to publish step#283

Merged
felipefreitag merged 1 commit intomainfrom
feat/npm-provenance
Apr 17, 2026
Merged

feat: add npm provenance attestation to publish step#283
felipefreitag merged 1 commit intomainfrom
feat/npm-provenance

Conversation

@felipefreitag
Copy link
Copy Markdown
Contributor

@felipefreitag felipefreitag commented Apr 17, 2026

Adds --provenance flag to npm publish so published packages include a signed attestation linking back to the source commit and workflow run.


Summary by cubic

Enable provenance attestation in the release workflow by adding --provenance to npm publish. This embeds a signed attestation linking each published package to the source commit and workflow run, improving traceability.

Written for commit 9459d85. Summary will update on new commits.

Adds --provenance flag to npm publish so published packages
include a signed attestation linking back to the source commit
and workflow run. The id-token: write permission is already in
place from trusted publishing.
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@felipefreitag felipefreitag merged commit 23c0a11 into main Apr 17, 2026
8 checks passed
@felipefreitag felipefreitag deleted the feat/npm-provenance branch April 17, 2026 16:36
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.

2 participants