ci(npm-publish): lock OIDC trusted publishing; correct changelog#79
Merged
Conversation
Add a workflow guard test asserting the npmjs publish job uses tokenless OIDC trusted publishing (id-token write, --provenance --access public) and references no NPM_TOKEN/NODE_AUTH_TOKEN, so a regression to long-lived tokens is caught. Correct the stale 0.4.1 NPM_TOKEN guidance forward in the 0.4.5 changelog. npm package-contents validation in release-pr already landed in #52. Closes #48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #48.
What
The npm-publish workflow already uses OIDC trusted publishing (
id-token: write,npm publish --provenance --access public) and tag/version parity. This PR makes that intentional and verifiable:test_npm_publish_workflow_uses_oidc_trusted_publishing) — asserts the publish job is tokenless OIDC (id-token: write,--provenance,--access public) and references noNPM_TOKEN/NODE_AUTH_TOKEN, so a regression back to a long-lived token is caught in CI.NPM_TOKENguidance in the 0.4.1 notes is corrected forward in the 0.4.5 entry (history left intact); npmjs auth is OIDC, no token required.npm package-contents validation in release-pr already landed in #52 (
scripts/inspect_npm_package.py). Provenance and tag/version parity were already present.Out of scope
GitHub Packages publish hardening (#47), shim pins, package identity.
🤖 Generated with Claude Code