chore: add pnpm minimumReleaseAge (48h) supply-chain delay#10
Conversation
Set minimumReleaseAge to 2880 minutes (48h) and add '@humanspeak/*' to the existing minimumReleaseAgeExclude list so first-party releases are not delayed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 27 minutes and 10 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Adds a 48-hour
minimumReleaseAge(2880 min) to the rootpnpm-workspace.yamlso freshly published dependency versions must age before install, mitigating supply-chain attacks.@humanspeak/*is prepended to the existingminimumReleaseAgeExcludelist so first-party releases are not delayed (existing pinned exclusions are preserved).Labeled
skip-publish(no release needed).