Pin trusted publishing workflow runtime - #3
Conversation
|
Warning Review limit reached
More reviews will be available in 27 minutes and 37 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates the npm publish workflow to use pinned versions of Node.js ( ChangesPublish Workflow Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/publish.yml:
- Around line 25-26: Replace the standalone version log with an equality check
that fails the job if PATH resolves a different npm binary: after the existing
npm install -g npm@11.5.1 step replace the plain npm --version step with a shell
check that compares $(npm --version) to "11.5.1" and exits non‑zero (and prints
a clear error) when they differ so the workflow stops before npm ci/publish.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e109bf66-5e8f-4bdf-aaf5-5fc51f8299f6
📒 Files selected for processing (1)
.github/workflows/publish.yml
Pins the publish workflow to Node 22.14.0 and npm 11.5.1 so npm trusted publishing can use an OIDC-compatible npm CLI.
Also removes npm package-manager caching from the release publish workflow. This does not publish npm, create tags, or change package metadata.
Summary by CodeRabbit