Repository navigation
ci: blast-radius report — leaf vs dependent classification per changed package - #643
Merged
Merged
Conversation
…d package Report-only sibling to trivial-update.yml (inbox#20's fast-path suite). For each package a PR changes: TRUE LEAF (no recipe imports it, no stack/profile names it — worst case is confined to the package itself), leaf-but-referenced, or direct + transitive dependent counts with the top importers named. Current catalog: 472 packages, 195 true leaves (41%). The two-source edge scan matters: stacks reference packages by NAME (build_packages = ["go", ...]), not by import, so an import-only scan misclassifies every stack tool as a leaf — verified ghidra/deno/lean/ gradle and 11 others are caught only by the name scan. String matching over-demotes, which is the safe direction for a classifier whose consumers may one day fast-path leaf updates. The summary's final line is stable and machine-readable (blast-radius: ALL-TRUE-LEAVES | HAS-DEPENDENTS) so a future auto-merge lane for trivial+leaf bumps can key on it without parsing the table. Composes with #250's check scoping (a leaf PR now builds and checks only itself) and the dwell/soak gate (auto-merged updates would still soak on main before stable promotion). Pure checkout scan, no network, never a required check. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Warning Review limit reached
On-demand reviews are free for the next 27 days. After that, they cost $0.25 per reviewed file. Or wait 17 minutes for your next included review. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Your 58 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
mitodrummer
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 of the leaf-update idea: make blast radius visible on every PR before any policy changes. Report-only, joins the dwell/smoke/trivial suite; same conventions (pinned checkout, SHAs via env, never a required check, errors downgrade to warnings).
Catalog today: 472 packages, 195 true leaves (41%). Heaviest: base (419 direct), toolchain (382), glibc (354 — 471 transitive).
Sample output for a mixed PR:
The final
blast-radius: ALL-TRUE-LEAVES|HAS-DEPENDENTSline is deliberately machine-readable — phase 2 (auto-merge for trivial ∧ all-leaves ∧ green pkgmgr bumps, if we decide to) keys on it plus trivial-update.yml without re-parsing. Design + governance discussion before enabling anything automatic.🤖 Generated with Claude Code