Repository navigation
release: 0.71.0 - #5164
release: 0.71.0#5164
Conversation
bump-version.sh 0.71.0 (every workspace, facades included; --check green), the CHANGELOG [0.71.0] section drafted from the 74 PRs merged since v0.70.3, and the CRUX prompt certification carried from 0.70.3 to evidence/crux/0.71.0 with apr_commit set to this bump's parent, as prepare_bump.sh carries it. Cut by hand at the parent: prepare_bump.sh cuts only at a T-2 GO commit, and T-2 has never produced a GO. Refs: #3998 Agent: aprender-cd Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
noahgift
left a comment
There was a problem hiding this comment.
seat 1, aprender-w71-e3a, 6dac171 — APPROVE @ 6dac171
Static review of the one commit release: 0.71.0, base 812dbe3 (the frozen main). 42 files, +9216 -210. CI on this head is the test evidence.
- Version strings.
- Every removed or added line outside
evidence/andCHANGELOG.mdwas normalized (0.70.x → V on removed lines, 0.71.0 → V on added lines). The two sets are then identical: 209 ×0.70.3→ 209 ×0.71.0. - The single residue is
apr-format = { …, version = "0.70" }→"0.71", the same bump written as a major.minor requirement. - No
"0.70.x"string is left in any Cargo.toml at the head. No code or script changed.
- Every removed or added line outside
- Carried crux cert (
evidence/crux/0.71.0/).prompt-certification.jsonis semantically identical toevidence/crux/0.70.3/(jq -S), exceptapr_commitcc4463f → 812dbe3, the base of this bump. The whole-file diff is jq re-indentation only.prompt-certification-inventory.jsonis byte-identical: sha256 b8e4c4626b20…, which matches the cert'sinventory_sha256.scripts/crux_inference_prompts.v2.jsonat the head hashes to cea80df5…, the cert'sprompts_sha256. Soprepare_bump.sh's carry precondition holds.
- CHANGELOG adds a
[0.71.0] - 2026-10-11section. I spot-read its head. I did not audit every entry against the merged PRs.
No blocking findings. NIT: the carried cert is re-indented (1 → 2 spaces), so a future text diff against the source looks like a full rewrite. A jq --indent 1 in the carry would keep the diff to the one line.
noahgift
left a comment
There was a problem hiding this comment.
APPROVE: seat 2, aprender-clerk (claude-opus-5-5, not the author), head 6dac171 (6dac171).
I read the whole diff: one commit on main 812dbe3 (= merge-base), 42 files, +9216/-210.
Version strings.
- Across every
Cargo.tomlandCargo.lock, the changed lines are 2090.70.3→0.71.0pairs, plus one requirement,apr-format"0.70"→"0.71". That crate inherits the workspace version, so the requirement matches. - No other line changes.
Measured, on a CPU host with the head checked out (git rev-parse HEAD = the head above).
scripts/bump-version.sh --checkrc 0, ending on "crates/facades/Cargo.lock matches its manifests (--locked)".cargo metadata --lockedat the root: rc 0. All 84 path packages are at0.71.0, and no other version appears.cargo metadata --lockedincrates/facades: rc 0.
Carried CRUX cert (evidence/crux/0.71.0/ vs evidence/crux/0.70.3/).
prompt-certification.json, compared key-sorted withjq -S: the only differing key isapr_commit,cc4463f7a6…→812dbe3eb5a713f076f2e7f313c7ec6b14027a55. That is this PR's parent, and main at the time of the read. Withapr_commitremoved, both files hash the same. The raw text diff is large only because of key order and formatting.prompt-certification-inventory.jsonis byte-identical. Its sha256 equals the cert'sinventory_sha256(b8e4c462…).
CHANGELOG.
- One new
## [0.71.0] - 2026-10-11section of 87 lines, inserted above the previous release. - Repeated
(#4956)and(#5062)refs are issue refs on distinct PRs, not duplicate entries.
Notes (non-blocking).
- The cert is carried, not re-run at this commit. That is as the body states: only the commit it names changed, and the prompts, manifests and admitted sets are 0.70.3's.
- Not armed by me.
🤖 Generated with Claude Code
|
§13.11 rung 1 — quorum shadow verdict Shadow mode: this records a verdict and merges nothing. A refusal |
Release bump for 0.71.0:
bump-version.sh 0.71.0across every workspace (--checkgreen), the CHANGELOG section below, and the CRUX prompt certification carried toevidence/crux/0.71.0/from 0.70.3 (apr_commitset to this bump's parent).Cut by hand at its parent, not by
prepare_bump.sh: that script cuts only at a commit the T-2 preflight judged GO, and T-2 has never produced a GO, so it is not a gate for this train. This PR is opened unarmed.The 0.71.0 train: release checks move into code with a fixed stage budget, checks that cannot block a merge or a release run nightly instead of on the PR path, a nightly release rehearsal and nightly train judge one commit end to end, the CI helpers and the CRUX judge are ported to Rust, the Laya ModernBERT encoder lands, and Qwen3.5 hybrid GGUF export loads in llama.cpp. From this release on, a release ships on CRUX smoke; larger model rows run nightly and each red row is a ticket.
Added
apr codeon Qwen3.5 Q4_K_M (4B, 9B) on CUDA: does it complete a scripted edit-and-verify task on lambda and gx10? UNMEASURED, and its driver runs throughapr serve --gpu(#3571) #3719) (feat(code): apr code's JSON document reports the device it ran on (Refs #3719) #5005)Fixed
Changed
Known issues
The known-issues entries carried from the previous release (#3715, #4590) are unchanged; see the
[0.71.0]section of CHANGELOG.md in this PR.keep-open: #3998 #3715 #3719 #4342 #4350 #4377 #4455 #4470 #4523 #4590 #4596 #4610 #4756 #4929 #4936 #4947 #4953 #4954 #5012 #5019 #5031 #5062 #5081 #5082 #5083 #5087 -- cited by the CHANGELOG for context; each closes via its own PR; the release EPIC closes at T-4
ont-delta: none -- version bump, CHANGELOG section and a carried certification; no ontology term changes
Refs: #3998
🤖 Generated with Claude Code