Skip to content

docs(proposals): global hook for build-system dependency post-processing#1272

Open
vshawrh wants to merge 1 commit into
python-wheel-build:mainfrom
vshawrh:docs/global-build-deps-hook-proposal
Open

docs(proposals): global hook for build-system dependency post-processing#1272
vshawrh wants to merge 1 commit into
python-wheel-build:mainfrom
vshawrh:docs/global-build-deps-hook-proposal

Conversation

@vshawrh

@vshawrh vshawrh commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a proposal document for extending fromager.hooks with a get_build_system_dependencies global hook point, allowing downstream projects to post-process build-system dependencies for all packages without per-package plugins.

The implementation is in a separate PR: #1271

Related issue: #1263

Document the motivation, design, hook signature, chaining behavior,
execution order, and interaction with existing mechanisms for the new
get_build_system_dependencies global hook point.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Vikash Shaw <vshaw@redhat.com>
@vshawrh
vshawrh requested a review from a team as a code owner July 24, 2026 16:01
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@vshawrh, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 14 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 05d58497-3909-4c4d-b7f5-8cb93e1acc10

📥 Commits

Reviewing files that changed from the base of the PR and between d249228 and 8c0b285.

📒 Files selected for processing (1)
  • docs/proposals/global-build-system-dependencies-hook.md

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant