fix(ci): use npm 11 via npx for publishing#43
Conversation
commit: |
There was a problem hiding this comment.
Pull request overview
Updates the npm publishing workflow to avoid a flaky global npm upgrade in CI while still publishing with npm v11 for trusted publishing/provenance support.
Changes:
- Removed the global
npm install --global npm@...step that was failing in CI. - Switched the publish step to run
npm@11.10.0vianpxwhile keeping the existing pnpm install flow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release-please workflow was modified to use a pinned npm version (11.10.0) for publishing instead of globally upgrading npm first. The global npm upgrade step was removed and the publish command now explicitly invokes the specific npm version via Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 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 |
Summary
Summary by CodeRabbit