chore: approve pnpm workspace builds - #3
Conversation
|
Warning Review limit reached
Next review available in: 4 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
05531e8 to
9b39e28
Compare
9b39e28 to
088d52e
Compare
pnpm v10+ has a security feature called approve-builds to explicitly approve which dependencies can run scripts during installations.
When
pnpm installdetects dependencies with build scripts, it blocks them by default and outputs a message instructing to runpnpm approve-buildsto explicitly allow which packages can execute their installation scripts.To make next project installations and contributions to be a bit more convenient - let's approve the existing dependencies. 😎
Additionally specify package manager & its version in the
package.jsonto ensure everyone are using the same version.