Disable new metrics packages & bump RPM builder#229
Conversation
|
Warning Review limit reached
Next review available in: 9 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe RPM build image moves to CentOS Stream 10. Downstream image specification filtering now removes additional metrics packages and install entries. ChangesRPM build image
Downstream spec filtering
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 `@packaging/rpm.Containerfile`:
- Line 3: Update the RPM build documentation describing the make rpm target to
reference the CentOS Stream 10 builder instead of Stream 9. Review the Stream 10
release/test instructions in docs/build.md and ensure they explicitly cover
supported CentOS 9 deployments where required, without changing the packaging
configuration.
🪄 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: CHILL
Plan: Pro Plus
Run ID: 6d7583d9-7131-42c9-80b9-0aa06924a6d0
📒 Files selected for processing (2)
packaging/rpm.Containerfilesrc/image/modify-spec.py
ee4ebad to
006fc54
Compare
| FROM localhost/microshift-okd-srpm:latest AS srpm | ||
|
|
||
| FROM quay.io/centos/centos:stream9 | ||
| FROM quay.io/centos/centos:stream10 |
There was a problem hiding this comment.
We still support CentOS 9, so I'm afraid upgrading to 10 for build might not work
Summary by CodeRabbit