Description
There has been a lot of churn lately due to dependencies making breaking changes (from the perspective of hatch).
Since this is a CLI, I'd like to request that all releases have their dependencies frozen, to prevent these kind of breakages from occurring when installing a released version from PyPI (via pip or uv).
I found hatch-build-freeze, which might make this easier, but it also appears to be a somewhat straightforward option that could be added directly to hatch. The general procedure would seem to be:
- Check for
pylock.toml (maybe falling back to uv.lock or other known lockfiles?)
- If none exists, generate one with current dependency resolution.
- When building, overwrite dependencies with locked versions.
NOTE: This request is specifically for hatch releases, but it would be a great feature to add to hatch/hatchling for other projects as well.
Use case/motivation
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Description
There has been a lot of churn lately due to dependencies making breaking changes (from the perspective of
hatch).Since this is a CLI, I'd like to request that all releases have their dependencies frozen, to prevent these kind of breakages from occurring when installing a released version from PyPI (via
piporuv).I found hatch-build-freeze, which might make this easier, but it also appears to be a somewhat straightforward option that could be added directly to
hatch. The general procedure would seem to be:pylock.toml(maybe falling back touv.lockor other known lockfiles?)NOTE: This request is specifically for
hatchreleases, but it would be a great feature to add to hatch/hatchling for other projects as well.Use case/motivation
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct