fix(python): ship PEP 561 markers for all published packages - #584
Conversation
There was a problem hiding this comment.
Warning — .github/workflows/test-integrations.yml, trigger/detect-changes hunks
Changes to .github/actions/test-python/action.yml now trigger this workflow, but none of the dorny/paths-filter Python filters match that path. Consequently, test-python is skipped and modifications to the shared action are never exercised; only the source-marker job runs. Add the shared action path to each Python filter or introduce a dedicated smoke test for the composite action.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Suggestion — integrations/ag2/python/pyproject.toml:25
The new ag2>=0.9.0,<1 constraint conflicts with the README’s documented requirement of ag2>=0.9.0, which implies 1.x compatibility. Update the README requirement to ag2>=0.9.0,<1 so users see the actual supported range.
No correctness or security issues found.
Summary
py.typedmarkers to all eight published Python integration packagesWhy
The integration sources are annotated and pass their strict mypy configurations, but their published wheels do not declare PEP 561 support. Type checkers therefore report
import-untypedand treat package APIs asAnyafter installation.This includes the
zep-adkchange proposed in #552 and applies the same fix to every published Python integration package.zep-ingestwas already correctly marked; the new guard covers it as well.Validation
py.typedis present and empty in every artifact