Release 0.11.4 - #170
Merged
Merged
Release 0.11.4#170
Conversation
Bump the version surfaces for the release that judges an edit (and a Codex apply_patch) as the file it would leave, and leaves Python bytecode out of a pack's lockfile hash; move the changelog entries from Unreleased to 0.11.4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Claude <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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Release preparation for 0.11.4, which carries two fixes.
#168: an edit is judged as the file it would leave.
Edit/MultiEditpayloads were judged as bare fragments, so a whole-file policy never saw them. Now the edit's replacements are applied to the file on disk and the result is judged.apply_patchgets the same treatment in the runtime: each file the patch touches is rebuilt from disk. Codex hooks are not wired pre-write yet.#169: Python bytecode is left out of a pack's lockfile hash. Before this,
chock checkreported an untouched pack as changed once a gate had run.The version surfaces are bumped exactly as in 0.11.3:
pyproject.toml,CITATION.cff, theaction.ymldefault,docs/installation.mdanddocs/reviewer-evidence.md;gen_brand_assets.py --checkreports it current);Unreleasedentries move under## 0.11.4.After merge: tag
v0.11.4on the merge commit and publish the GitHub release. The tag push runsrelease.yml(PyPI and binaries).Definition of done
chock check→ 0 errors, 0 warnings, 0 infoschock check --only matrixpasses; no behaviour change in this PRchock sync --repo . --checkcleanchock check --only verifycleanpytest -q: code unchanged since Judge an edit as the file it would leave, not as its fragment #168/Leave Python bytecode out of a pack's lockfile hash #169, both green on 3.11–3.13; CI re-runs it hereinit,addor hook change in this PRruff check .andruff format --check .cleanClaims
🤖 Generated with Claude Code
https://claude.ai/code/session_01CzNYfzP8ymU3r4JB9Sz8Ha
Generated by Claude Code