ci: report-only dwell (soak) check for main -> stable (inbox#20/#21) - #397
Conversation
The soak gate for main -> stable promotion is DWELL: how long a package's current version has lived on `main` (git-derived), per inbox#20's key reframe. #279 (upstream version-age) and #280 (stable closure) landed; the dwell signal itself was the missing piece. This adds it, report-only. `dwell_report.py` computes, per package, the commit date at which its current `main` version was introduced (a single `git log -S` pickaxe on the quoted version token, first-parent), and compares `main` vs `stable` to classify each package: promotable (dwelled >= 7d and differs from stable), soaking (< 7d), or already in stable. Pure git — no `minimal dump`, no network, no secrets. `dwell.yml` runs it on workflow_dispatch + a daily schedule (the "what's promotable to stable" dashboard over the full catalog) and on pull_request into `stable` (per-changed-package dwell — the promotion gate preview). Hardened to stay green exactly like version-age.yml (pinned action SHA, env-passed SHAs, contents:read, report-only) and MUST NOT be a required check. Matches the "report-only spec first" strategy: observe what it would gate on real promotions before wiring it to required. 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: 55 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
The soak gate for
main→stablepromotion is dwell — how long a package's current version has lived onmain(git-derived) — per the key reframe in gominimal/inbox#20. The two supporting-data checks already landed report-only (#279 upstream version-age, #280 stable runtime-closure); the dwell signal itself was the missing piece. This adds it, report-only, matching the "spec-first, gate later" strategy.What
.github/scripts/dwell_report.py— for each package, finds the commit date at which its currentmainversion was introduced (a singlegit log -Spickaxe on the quoted version token, first-parent — so a non-version edit tobuild.ncldoesn't reset the clock, and a version prefix like1.2.3can't false-match1.2.30). Comparesmainvsstableand classifies each package:stableand has dwelled ≥ 7d inmainstable, < 7dstablePure git: no
minimal dump, no network, no secrets. Runs the full catalog in ~10s..github/workflows/dwell.yml— runs it:workflow_dispatch+ dailyschedule→ full-catalog "what's promotable tostable" dashboardpull_requestintostable→ per-changed-package dwell (the promotion gate preview)Hardened exactly like
version-age.yml(pinned action SHA, env-passed SHAs,contents: read, report-only) and must not be added to branch-protection required checks.Sample output (full catalog, today)
Notes
%cIemits a trailingZ, normalized forfromisoformatcompatibility below 3.11).pull_request: [stable]trigger activates once this file reachesstable(GitHub reads the workflow from the PR base branch); the dispatch/schedule modes work immediately frommain.Closes part of gominimal/inbox#20 (dwell soak criterion) · building block for gominimal/inbox#21.
🤖 Generated with Claude Code