Skip to content

Protect npm publishing with package-release environment - #254

Draft
jikoong wants to merge 1 commit into
masterfrom
jikoong/protect-react-connect-js-package-release
Draft

jikoong wants to merge 1 commit into
masterfrom
jikoong/protect-react-connect-js-package-release

Conversation

@jikoong

@jikoong jikoong commented Nov 3, 2026

Copy link
Copy Markdown

Require both GA and preview npm publishing jobs to use package-release, and default workflow permissions to read-only. Publishing jobs retain the permissions needed for npm OIDC and GitHub releases. This is the same five-line change as stripe/connect-js#334.

Rollout prerequisites:

  • Before merge, protect master with independent review and the required test check, configure package-release to allow only that branch, and set repository Actions permissions to read-only.
  • After merge, configure the @stripe/react-connect-js npm trusted publisher for stripe/react-connect-js / npm_auto_release.yml to require package-release. Coordinate that change with the next intended release.

Validation: YAML parsing, structural comparison, and git diff --check passed. Release triggers, steps, package versions, and existing job permissions are unchanged. Live publishing remains to be verified.

Committed-By-Agent: codex
Co-authored-by: codex <noreply@openai.com>
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.

1 participant