🔧 build: migrate from hatch to tox with ty #415
Merged
+301
−261
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 platformdirs project was the last tox-dev project still using hatch for environment management. 🔧 Migrating to tox aligns it with the rest of the ecosystem (filelock, tox, etc.) and brings consistency to how all tox-dev projects are developed and tested.
This replaces hatch environments with a
tox.tomlconfiguration covering test, fix, coverage, type checking, docs, package metadata validation, and dev environments. Theoptional-dependenciessections move to PEP 735dependency-groups, andmypyis replaced bytyfor type checking. CI workflows now installtox+tox-uvinstead ofhatch, ReadTheDocs builds docs through tox, andtox-toml-fmtis added to pre-commit.Coverage path mappings are updated for tox's
.tox/layout. The release workflow bumps to Python 3.14. All existing functionality (multi-version testing, coverage aggregation, docs, linting) is preserved under the new runner.