fix(release): record the z3 verdict — the bump is fine, and the hold has still never caught anything - #1212
Merged
Merged
Conversation
…roduced; the bump is FINE and the hold has still never caught anything v0.64 published a fabricated attribution (#1108 "breaks the Bazel build", on a mechanism `crates/BUILD.bazel:167-170` says cannot occur) and retracted it. The retraction then promised a remedy that never fired: `@dependabot recreate` on a CLOSED PR does nothing. So "sent for recreate and a real verdict" was itself an unkept promise — a smaller instance of the same defect the retraction was about. The bump was raised by hand in #1202 with NO PREDICTION ATTACHED, because predicting was the original error. CI answered: Bazel Build & Proofs pass Z3 Verification pass (the separate --features z3-solver build) 9/9 required, 0 failures z3 0.20.2 -> 0.21.0, pulling z3-sys 0.11 -> 0.13, does NOT break the Bazel build. The 504 fetching bazel-skylib was the whole story. Merged. CONSEQUENCE, stated because it is the part that mattered: the enforced dependabot hold has STILL never caught a breaking 0.x-minor. It remains unfalsified. v0.64 published the opposite as its headline evidence for that gate, which is precisely why the claim was worth retracting — a rule that gets credit it has not earned is worse than one with no evidence, because nobody looks again. Recorded by APPENDING the outcome rather than rewriting the original correction: both the fabrication and its resolution stay visible, which is the same discipline applied to VG-009 and to the FLOORPROSE premise. Verified: rivet at main's 40-error cross-repo baseline with 0 broken cross-refs, status_evidence exit 0, claim_check 62/62. Refs #965, #849, #836
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The z3 verdict CI actually produced — and what it says about the gate
v0.64 published a fabricated attribution (#1108 "breaks the Bazel build", on a
mechanism
crates/BUILD.bazel:167-170says cannot occur) and retracted it. Theretraction then promised a remedy that never fired:
@dependabot recreateona closed PR does nothing. "Sent for recreate and a real verdict" was itself an
unkept promise — a smaller instance of the same defect.
So the bump was raised by hand in #1202, with no prediction attached,
because predicting was the original error. CI answered:
Bazel Build & ProofsZ3 Verification(the separate--features z3-solverbuild)z3 0.20.2 → 0.21.0 does not break the Bazel build. The 504 fetching
bazel-skylibwas the whole story. Merged.The consequence worth stating
The enforced dependabot hold has still never caught a breaking 0.x-minor. It
remains unfalsified — which is the honest state, and exactly why claiming
otherwise mattered. A rule that gets credit it hasn't earned is worse than one
with no evidence at all, because nobody looks again.
Recorded by appending the outcome rather than rewriting the original
correction, so both the fabrication and its resolution stay visible — same
discipline applied to VG-009 and the FLOORPROSE premise.
Refs #965, #849, #836