Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughEnables pip caching and updates cache keying, expands hardened-runner endpoints, adds attestation creation and verification steps for binary installers and Python distributions, updates installation docs, and ignores ChangesBuild, Caching, and Attestations
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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/build.yml:
- Around line 72-86: The gem install in the "Install fpm" step currently uses
--install-dir vendor/fpm-gems but not --bindir, so the fpm executable is not
placed in vendor/fpm-gems/bin referenced by the "Add fpm to PATH" step; update
the Install fpm step to add --bindir vendor/fpm-gems/bin (i.e., run gem install
--no-document --install-dir vendor/fpm-gems --bindir vendor/fpm-gems/bin fpm
--version 1.17.0) so the binary lands in vendor/fpm-gems/bin and the PATH entry
is correct.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 0883e4a7-3ff9-4f79-b016-14097deee6a5
📒 Files selected for processing (3)
.github/workflows/build.yml.gitignoredoc/tutorials/installation.rst
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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/build.yml:
- Around line 93-96: Add an extra, more general restore-keys fallback for the
existing restore-keys block (the lines using the key pattern ${{ github.job
}}-${{ matrix.platform }}-${{ github.ref_name }}-${{ hashFiles('pyproject.toml')
}}) so caches can be shared across branches: include one fallback that omits ${
{ github.ref_name } } but keeps the hash (e.g. ${{ github.job }}-${{
matrix.platform }}-${{ hashFiles('pyproject.toml') }}-) and optionally a broader
fallback without the hash (e.g. ${{ github.job }}-${{ matrix.platform }}-) for
both the ccache and clcache restore-keys blocks to improve cross-branch cache
hits while preserving content-addressed safety.
- Line 50: Replace the broad wildcard entry '*.blob.core.windows.net:443' in the
egress allowlist with the specific Azure Blob Storage hostnames required by the
build (e.g., the concrete storage account subdomains used during artifact
fetches), update the allowlist entry in the workflow where the current
'*.blob.core.windows.net:443' string appears, and add a short inline comment in
the same build.yml egress section documenting which specific subdomains are
allowed and why (or add a TODO to enumerate them) so the policy is not overly
permissive.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 5b5fecdc-ab08-4934-a65c-21cb76ac27e3
📒 Files selected for processing (2)
.github/workflows/build.ymldoc/tutorials/installation.rst
1 participant
Summary by CodeRabbit
Documentation
Chores