fix: add npm auth verification step before publish - #21
Conversation
Adds a pre-publish check that verifies the NPMJS_TOKEN secret exists and can authenticate with npm. This surfaces auth issues as clear errors instead of misleading 404s from the registry.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe npm release workflow now verifies that Changesnpm release authentication
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Addressed Issues:
Fixes #(issue number)
Screenshots/Recordings:
Additional Notes:
Adds a pre-publish check that verifies the NPMJS_TOKEN secret exists and can authenticate with npm. This surfaces auth issues as clear errors instead of misleading 404s from the registry.
Checklist
We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.
Summary by CodeRabbit