fix: Apply OIDC auth to publish packages#46
Conversation
|
📝 WalkthroughSummary by CodeRabbit
WalkthroughRemoved the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Pre-merge checks and finishing touches✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
Summary
This commit transitions the package publishing workflow from token-based authentication to OpenID Connect (OIDC) authentication by removing the explicit
NPM_TOKENenvironment variable reference from the GitHub Actions workflow configuration.Technical Details
The modification involves removing the
NPM_TOKENsecret environment variable from the changesets publishing step in .github/workflows/publish.yml. This change reflects the adoption of OIDC-based authentication, which provides a more secure authentication mechanism by eliminating the need for long-lived, static authentication tokens.Security and Operational Benefits
Enhanced Security Posture:
Improved Operational Efficiency:
Implementation Context
The workflow maintains the
permissions: write-allconfiguration, which grants the necessary permissions for the GitHub Actions job to obtain OIDC tokens and authenticate with npm's registry. The changesets/action package publishing mechanism remains unchanged, with only the authentication method being modernized.This change aligns with current best practices for GitHub Actions security and npm registry authentication patterns.