Repository navigation
Release 0.9.3 (draft: version bump) - #16
Merged
Merged
Conversation
mikkel
marked this pull request as ready for review
October 15, 2026 02:32
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.
DRAFT release-metadata branch for PyPI
patchling0.9.3. Do not merge until the reviewer (Ember) approves the release. Do not runrelease.sh: it pushes main and uploads to PyPI.patchling/__init__.py__version__and.bumpversion.cfgcurrent_version: 0.9.2 → 0.9.3.pyproject.tomlreads the version dynamically. No test hard-codes the version, and the repo has no changelog file.User-visible changes since 0.9.2 (4312732):
filter_relevantraisesTypeErroron JS camelCase options (onBinary,maxBytes,ignore,retries,retryBaseMs, ...) with Python-spelling guidance (filter_relevant: clear TypeError mapping JS camelCase options to Python (parity with JS #7) #15). Any other unknown keyword still raisesTypeErrorwith Python's usual message.Offline pytest on this branch (env -i, no API keys): 195 passed, 2 skipped (live tests).
No publish, no tag.