Skip to content

fix: use node 24 trusted publishing#112

Merged
jasonsuhari merged 1 commit into
mainfrom
fix/release-trusted-publishing
Jul 9, 2026
Merged

fix: use node 24 trusted publishing#112
jasonsuhari merged 1 commit into
mainfrom
fix/release-trusted-publishing

Conversation

@jasonsuhari

Copy link
Copy Markdown
Owner

Summary

  • use Node 24 in the release workflow so npm satisfies trusted-publishing requirements without installing npm@latest on Windows
  • stop passing --provenance on the trusted-publishing/OIDC path, since npm automatically generates provenance for trusted publishing
  • keep --provenance for the NPM_TOKEN fallback path

Closes #109.

Validation

  • git diff --check
  • inspected release workflow publish paths

Signed-off-by: Jason Matthew Suhari <jasonmatthewsuhari@gmail.com>
@jasonsuhari jasonsuhari merged commit 7e70232 into main Jul 9, 2026
3 checks passed
@jasonsuhari jasonsuhari deleted the fix/release-trusted-publishing branch July 9, 2026 04: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.

Fix release workflow npm pack parsing

1 participant