[SC-16431] Limit build contents to reduce PyPI package size#520
Conversation
Restrict Hatch build outputs to the package and required metadata so release artifacts stay under PyPI's file size limit. Remove the stale test-generation CLI reference to keep contributor docs aligned with the current repo layout. Co-authored-by: Cursor <cursoragent@cursor.com>
PR SummaryThis PR introduces several changes that affect the packaging configuration and the test creation workflow: • The version numbers have been updated from 2.13.3 to 2.13.4 in various project files (pyproject.toml, DESCRIPTION, uv.lock, version.py). (Note: Version bumps are considered trivial and are not the focus of this summary.) • A new packaging configuration has been added using Hatch. The PR defines explicit sdist and wheel targets with specified inclusion and exclusion rules. This ensures that only the necessary files are packaged, helping to maintain a clean distribution. • The project’s test creation mechanism has been modified. The console script registration for generating new tests (vm-create-new-test) has been removed from pyproject.toml, and the corresponding documentation in scripts/README.md has been updated. Users are now instructed to manually create new tests by adding files to the appropriate directory and following the established naming and structure patterns. Test Suggestions
|
Pull Request Description
What and why?
Restricted the Hatch build outputs so published artifacts only include the validmind package and required release metadata. This reduces the source distribution from over PyPI’s 100 MB limit to about 20 MB, preventing upload failures, and removes a stale console-script reference plus outdated docs for a non-existent test-generation script.
How to test
Run
uv buildand confirm the generateddist/*.tar.gzanddist/*.whlfiles are created successfully. Verify the source distribution is below PyPI’s 100 MB limit and does not include repo-only directories such asnotebooks/,docs/,.github/,scripts/, or the top-leveltests/.What needs special review?
Dependencies, breaking changes, and deployment notes
Release notes
Checklist