Repository navigation
Update Python support, typing, and package publishing - #18
Merged
Merged
Conversation
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.
The package still used Pipenv, Black, mypy and legacy setup.py publishing, with CI and release jobs targeting older Python versions. Version 0.3.0 supports Python 3.11+ and uses Python 3.15.2 for development, with uv-managed dependencies and builds, Ruff linting/formatting, and ty checks.
Request JSON and response models now validate data at the boundary. Typed metadata, currency/status contracts and a py.typed marker preserve useful types for downstream consumers. Shop resources depend on an independent transport protocol, so annotations resolve at runtime without TYPE_CHECKING imports.
CI builds distributions once, tests the installed wheel and its exported types on Python 3.11–3.15, and makes the publishing workflow wait for those checks. Releases verify that the tag matches the package version and publish the same tested artifacts through uv and PyPI trusted publishing. The dynamic version file is included in uv's cache keys so version changes refresh installed metadata.
Validation:
GitHub Actions passed the build and all five Python-version test jobs on the final commit
e9e3df6(run).