chore(deps): update actions/setup-node digest to 48b55a0 - #396
Conversation
|
Warning Review limit reached
More reviews will be available in 50 minutes and 27 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 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 (3)
📝 WalkthroughWalkthroughThis PR updates the pinned Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
1af8a9d to
a44a128
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #396 +/- ##
=======================================
Coverage 84.51% 84.51%
=======================================
Files 153 153
Lines 8093 8093
Branches 2189 2189
=======================================
Hits 6840 6840
Misses 1252 1252
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
9d79b47 to
e5526ec
Compare
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/cd-pypi-cli.yml:
- Around line 35-38: The actions/setup-node step in the release workflow is
susceptible to cache poisoning attacks from untrusted PR runs because it uses
the standard pnpm cache that is shared across all workflows. To fix this
security vulnerability, either disable caching by changing `cache: 'pnpm'` to
`cache: false` to prevent any cache restoration during releases, or implement
cache isolation by replacing the cache property with a unique
cache-dependency-path (such as 'release-pnpm-lock.yaml') to ensure release
builds use a separate, dedicated cache that cannot be poisoned by PR workflows.
The first option (disabling cache) is simpler and more secure for release
workflows.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 783afa81-51ff-4425-afea-75a28cf18bc6
📒 Files selected for processing (3)
.github/workflows/cd-pypi-cli.yml.github/workflows/cd.yml.github/workflows/ci.yml
e5526ec to
6b7a20a
Compare
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/cd.yml:
- Around line 50-53: The release publish job in the workflow is reusing the
shared pnpm cache, which can be restored from untrusted PR runs. Update the
setup-node step in the release workflow to disable automatic pnpm caching or
switch to a release-only cache key so the publish job does not consume caches
written by CI runs. Use the existing setup-node configuration in the workflow to
locate the change.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f8d24f30-2b5f-412f-81ec-ad8ab9f77320
📒 Files selected for processing (3)
.github/workflows/cd-pypi-cli.yml.github/workflows/cd.yml.github/workflows/ci.yml
🚧 Files skipped from review as they are similar to previous changes (1)
- .github/workflows/ci.yml
6b7a20a to
1adabfd
Compare
1adabfd to
eb6f459
Compare
This PR contains the following updates:
53b8394→48b55a0Configuration
📅 Schedule: (in timezone UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Summary by CodeRabbit