ci: wire Linux evidence drift into release gate#141
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughAdds an official Linux distro evidence-drift validation target, includes it in Gate 2, documents its release-gating behavior, and tests successful execution, failure propagation, and documentation coverage. ChangesOfficial evidence drift validation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
|



Summary
Wire the Linux official distro evidence drift audit into the canonical ECLI release gate.
This PR makes official distro evidence drift release-visible and release-blocking through
make validate-gate2.What changed
Added the canonical Make target:
The target runs:
The target is wired into:
The Python provisioning script remains the single source of truth for official evidence drift detection.
Failure behavior
The Make target does not mask exit codes.
If the Python gate exits
2because official distro evidence drift is detected:make validate-official-evidence-driftfails;make validate-gate2stops;Tests
Added coverage proving:
validate-gate2invokes the official evidence drift gate;2propagates as a failing release gate;Documentation
Updated:
docs/release/release-checklist.mddocs/release/artifact-contract.mddocs/release/packaging-flows.mdPreserved invariants
This PR does not:
OS_PACKAGE_NAMES;Validation
Passed:
Observed:
Existing unrelated validation failure
The new official evidence drift gate runs and passes inside:
The target later fails in the pre-existing PyPI artifact validation because the local ignored release tree does not contain:
The local release tree stores checksum files under
.checksums/, while the existing per-artifact Make target expects a top-level sidecar.This unrelated checksum-layout behavior is intentionally not modified in PR #141.
Summary by CodeRabbit
New Features
Documentation
Tests