Repository navigation
Prepare patchling 0.9.5 release metadata and compatibility notes - #35
Merged
Merged
Conversation
mikkel
marked this pull request as ready for review
November 9, 2026 04:44
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.
Prepare patchling 0.9.5 after the CLI/cache fixes merged in #34. The official PyPI latest is 0.9.4, and 0.9.5 is absent. The separate legacy gptdiff shim already depends on patchling and needs no release.
Synchronize the package constant and .bumpversion.cfg, add accurate release notes, preserve the already-shipped model change under 0.9.4, and document strict CLI failures plus the .lock/ sidecar and old-writer limits. Use separate cache files while npm patchling <=0.3.1 or Python <=0.9.4 writers remain; merging JS does not upgrade installed npm clients. The source distribution includes its changelog, cache protocol and version configuration. The README agent loop now stops on an apply failure.
Validation: fresh Python 3.10 environment, full offline suite 252 passed / 2 skipped; wheel and source distributions built, strict twine checks passed; artifact contents/metadata/license/type marker/four CLI entrypoints verified; fresh wheel and sdist installations outside the checkout report 0.9.5, pass pip check and coordinated-cache smoke checks. No dependency or Python-support change.
Publication is pending and no tag or PyPI upload has occurred. Version 0.9.5 is not yet available on the index. This is release preparation only. The existing release.sh is not run because it pushes all tags and main before validation and triggers documentation deployment.
Before merging this new exact head, route it through Ada. The eventual squash commit must use [skip ci] to suppress the unrelated main-push documentation deployment; this also skips push CI, so use green PR CI plus artifact validation and report that distinction. No credential changes, JS npm publication or unrelated deployment is included.