build(postgres): refresh Rust 1.98 digest contract - #331
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughPostgreSQL Dockerfile의 Rust toolchain 이미지를 1.98로 갱신했습니다. 새 immutable digest 계약 테스트를 반영했습니다. 백업 및 스키마 증거 레지스트리의 stale weakref 콜백 동작을 검증하는 회귀 테스트를 추가했습니다. Changes의존성 갱신
증거 레지스트리 회귀 검증
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This updates the pinned Rust build image and adds regression coverage for registry cleanup behavior. No current merge-blocking risk is identified. 🚥 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 |
Rust 1.98 immutable build-input contract — Draft child of #233
This successor preserves Dependabot #326's production delta without closing or discarding it. Protected
mainis exactbdff1273d3885dedc5187632e1c8838b470c9b6d; no direct protected-main write, force push, destructive rebase, or predecessor-evidence transfer was used.TDD lineage
38706b509eccabfa5dfd36af7e46916d5d05c2da: move the PostgreSQL image build to Rust 1.98 while the immutable dependency contract still requires the old digest;test_container_build_inputs_use_reviewed_immutable_digestsrejects the mismatch.927a1b8eb4b7013b52852f5ce256daea271b14fb: bindrust:1.98-slim-bookwormto reviewed digestsha256:1469a27c125cb5a3aebfa4f4e4665d935b02fb72cc093b2c974b3d740e43f157in the repository-owned contract.2edc2d3701f6695e3f656dae0e028e77d732d5d7: non-destructively reconciled protected fix(ci): revert docs-only paths-ignore, unsafe for this repo's doc-content contract tests #332, preserving its behavior-bearing CI correction.Coverage RCA and dependency-root repair
Exact-head CI
33721095260on2edc2d3701f6695e3f656dae0e028e77d732d5d7checked out the contributor head successfully. Compile, lint, public-docstring coverage, Python unit lanes, and PostgreSQL/container runtime smokes passed; theCoverage, docstrings, lint, and packagejob failed specifically atEnforce line coverage. The Rust 1.98 PR changes only the Dockerfile plus the immutable-input regression; the repository-wide inherited recovery-evidence weakref coverage arcs are already owned by dependency-root #233 rather than this lane.Current head
b64227c0fd5a10bf7ba0ca0b53a72f0180173ebetherefore non-destructively composes exact #233 head32469711f9a26a26ebcf4a7efcf20938bfdc94dbas a merge parent and carries its one test blob without copying that test as independent authority. The PR base is now #233's branch. Fresh compare from exact #233 to this head is ahead / zero behind and the relative diff remains exactly:docker/postgres/Dockerfile— Rust 1.98 immutable tag+digest;tests/test_dependency_refresh_contract.py— matching reviewed immutable-input contract.No #233 production/test delta appears in this PR-relative diff. This is the causal stack repair for the inherited coverage failure, not a coverage-gate bypass.
Current validation / integration boundary
All workflow/review evidence on
2edc2d370...or earlier heads is historical after this restack. Reacquire exact-current-head CI/security/SAST/Scorecard/OSV/release/review/thread evidence forb64227c0fd5a10bf7ba0ca0b53a72f0180173ebefrom scratch. Keep this PR Draft while #233 is unintegrated and while any current required gate is non-terminal.After #233 reaches protected main, reconcile/retarget this child non-destructively onto the then-current protected base, prove the unique two-file delta again, and reacquire every exact-final-head/current-base quality, security, coverage, package, SBOM/provenance, release, review, and thread gate required by live governance.
Do not self-approve, routinely bypass protection, weaken gates, transfer stale/predecessor evidence, or close Dependabot #326 until complete successor inheritance is reverified against the final integrated result.
Summary by CodeRabbit