release: 3.10.1 — ship the nine fixes that missed the 3.10.0 tag - #1613
Merged
Conversation
The nine defect fixes from #1603 merged after `v3.10.0` was tagged at `5b69202`, so the published 3.10.0 artifacts do not contain a single one of them — a user who installs 3.10.0 today still hits #1582 (verbatim reads capped at 4096 tokens), #1586 (an OpenCode config replaced by a lean-ctx-only scaffold), #1604 (flattened `ctx_call` losing its arguments) and the rest. This patch release exists to close that window; it adds no features. Version bumped in every coupled location the release gates check, plus one they do not: rust/Cargo.toml + Cargo.lock 3.10.0 -> 3.10.1 packages/lean-ctx-bin/package.json 3.10.0 -> 3.10.1 packages/pi-lean-ctx/package.json 3.10.0 -> 3.10.1 packages/pi-lean-ctx/package-lock 3.9.20 -> 3.10.1 (stale since 3.10.0) tests/delivery/test_check_release_tag.py — repository-tag assertion `check-package-versions.py` reads only the two `package.json` files, which is why the pi lock file sat at 3.9.20 through the 3.10.0 release without failing anything. It is corrected here rather than left to drift further. The CHANGELOG `[Unreleased]` section becomes `[3.10.1]` and states plainly that these fixes are absent from 3.10.0, so someone reading the notes after hitting one of the defects can tell which tag carries the fix. Pre-release gate (docs/ga/release-checklist.md §1), all from this branch: cargo test --lib 10538 passed, 0 failed, 22 ignored cargo clippy --all-features -D warn clean cargo fmt --check clean cargo build --release ok; binary reports 3.10.1 leanctx-verify tests + clippy clean python-lean-ctx pytest 118 passed, 3 skipped (Preview) check-package-versions.py engine 3.10.1, both packages match check-release-tag.py v3.10.1 accepted tests/delivery/test_check_release_tag 9 tests ok check-sdk-versions.py lean-ctx-python 1.0.0 check-narrative-governance.py passed scripts/loc-gate.sh ok lean-ctx doctor (clean HOME, release binary) 33/38, misses are setup-only Python remains labelled Preview. No claim promotion, no new capability. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Patch release. The nine defect fixes from #1603 merged after
v3.10.0was tagged at5b69202, so the published 3.10.0 artifacts contain none of them. Anyone installing 3.10.0 today still hits #1582, #1585, #1586, #1596, #1598, #1599, #1602, #1604 and #1605. This release closes that window and adds nothing else.Version bump
rust/Cargo.toml+Cargo.lockpackages/lean-ctx-bin/package.jsonpackages/pi-lean-ctx/package.jsonpackages/pi-lean-ctx/package-lock.jsontests/delivery/test_check_release_tag.pyThe pi lock file was still on 3.9.20 — it went through the entire 3.10.0 release without failing anything, because
check-package-versions.pyreads only the twopackage.jsonfiles. Corrected here rather than left to drift.Pre-release gate —
docs/ga/release-checklist.md§1Run from this branch:
cargo test --libcargo clippy --all-features -- -D warningscargo fmt --checkcargo build --releaselean-ctx 3.10.1 (official)leanctx-verifytests + clippypackages/python-lean-ctxpytestcheck-package-versions.pycheck-release-tag.py v3.10.1tests/delivery/test_check_release_tag.pycheck-sdk-versions.pylean-ctx-python1.0.0check-narrative-governance.pyscripts/loc-gate.shlean-ctx doctor, clean HOME, release binaryv3.10.0 post-release verification, for the record
Done retroactively while preparing this (
docs/ga/release-checklist.md§3):verify-release-integrity.py verify --tag v3.10.0→"verified": true,"errors": []across all 14 checks (manifest-tag, sbom-sha256, sbom-format, checksums-sha256, and each of the 10 artifacts)release-manifest.json↔SHA256SUMS→ all 10 hashes identical,checksums_sha256matchesaarch64-apple-darwinartifact →lean-ctx doctor33/38No feature work, no claim promotion, no capability status change.
🤖 Generated with Claude Code