ci: report-only trivial-update diff-audit (inbox#20/#21) - #399
Conversation
inbox#20's `#trivial` fast-path: an update is trivial when only the version and source hash(es) change and the version increases — no new features/deps/patches, so it can promote on a green build without functional re-validation. This audits each changed package's build.ncl diff and reports trivial vs non-trivial (naming the lines that make it non-trivial), so a `#trivial` label can be cross-checked. trivial_update_report.py: per package, every added/removed build.ncl line must be a `version = "..."` or a `*sha256 = "..."` and the version must increase, else non-trivial. Conservative by design — a false "trivial" would wave through a functional change. Pure git diff; no dump, no network, no secrets. Runs on pull_request into main. Hardened like version-age.yml; MUST NOT be required. Fifth report-only promotion signal after #279/#280/dwell/smoke-test. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 44 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 Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Why
inbox#20's
#trivialfast-path: an update is trivial when it changes nothing but the version and its source hash(es) and the version increases — no new features/deps/patches — so it can promote on a green build without functional re-validation. The criterion calls for a "CI diff-audit (only version/sha256 changed; version increases)" to back the#triviallabel. This is that audit — the fifth report-only promotion signal, after #279 (version-age), #280 (closure), dwell (#397), and smoke-test coverage (#398).What
trivial_update_report.pyaudits each changed package'sbuild.ncldiff (base..head): every added/removed line must be aversion = "..."or a*sha256 = "..."and the version must strictly increase — otherwise non-trivial, and it names the offending lines. Pure git diff: nominimal dump, no network, no secrets.trivial-update.ymlruns it onpull_request → main. Hardened likeversion-age.yml(pinned action SHA,contents: read, report-only); must not be a required check.Conservative by design: a false "non-trivial" just means the normal review path, but a false "trivial" would wave through a functional change — so the bar is strictly "only version + hash, nothing else."
Validated against real history
20250814.1 → 20260526.0+ a gcc-15 patch0.72.0 → 0.74.026.1.22 → 26.5.62.14 → 2.15.10.130.0 → 0.144.1Notes
#trivialPR label should be cross-checked against this audit before taking the fast-path.2.46.1, and date-versions like20260526.0); unparseable orderings are noted, not failed.Building block for gominimal/inbox#20 (
#trivialcriterion) · gominimal/inbox#21.🤖 Generated with Claude Code