Why migrate to Trusted Publishing?
As part of npm's security improvements, Cypress is migrating all GitHub Actions repositories from granular access tokens to npm Trusted Publishing (OIDC).
Benefits:
- Enhanced Security: Eliminates long-lived tokens that can be compromised, using temporary, job-specific credentials instead
- No Token Rotation: Removes the overhead of quarterly token rotation (previously required every 90 days)
- Automatic Provenance Attestation: Provides better audit trails and security transparency
- Simplified Security Model: Reduces attack surface by eliminating persistent credentials
Implementation
Update semantic-release
Update semantic-release from 24.2.3 to 25.0.1 inside the github workflow, which adds support for trusted publishing. See the release notes for details.
Configure Trusted Publishing
- Set up npm Trusted Publishing in the npm dashboard for
@cypress scope packages
- Update the GitHub Actions workflow to use OIDC instead of
NPM_TOKEN secret
- Remove the
NPM_TOKEN secret from repository settings once migration is complete
Reference
Acceptance Criteria
Why migrate to Trusted Publishing?
As part of npm's security improvements, Cypress is migrating all GitHub Actions repositories from granular access tokens to npm Trusted Publishing (OIDC).
Benefits:
Implementation
Update semantic-release
Update
semantic-releasefrom24.2.3to25.0.1inside the github workflow, which adds support for trusted publishing. See the release notes for details.Configure Trusted Publishing
@cypressscope packagesNPM_TOKENsecretNPM_TOKENsecret from repository settings once migration is completeReference
Acceptance Criteria
NPM_TOKENsecret removed from repository