Skip to content

ci: blast-radius report — leaf vs dependent classification per changed package - #643

Merged
bryan-minimal merged 1 commit into
mainfrom
feat/blast-radius-report
Sep 14, 2026
Merged

bryan-minimal merged 1 commit into
mainfrom
feat/blast-radius-report

Conversation

@bryan-minimal

Copy link
Copy Markdown
Member

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:

package dependents blast radius
bat TRUE LEAF itself only
ghidra leaf, referenced by stacks/reveng stack sessions
zlib 62 direct / 471 transitive 471 packages rebuild

The final blast-radius: ALL-TRUE-LEAVES|HAS-DEPENDENTS line 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

…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>
@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

  • Run on-demand review

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 details

Limit 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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0c4530f9-c976-4772-81a0-01aa41353c96

📥 Commits

Reviewing files that changed from the base of the PR and between 41d83f1 and 36615ea.

📒 Files selected for processing (2)
  • .github/scripts/blast_radius_report.py
  • .github/workflows/blast-radius.yml

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

@bryan-minimal
bryan-minimal added this pull request to the merge queue Sep 14, 2026
Merged via the queue into main with commit 08ad242 Sep 14, 2026
11 checks passed
@bryan-minimal
bryan-minimal deleted the feat/blast-radius-report branch September 14, 2026 19:41
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.

2 participants