Pip-deepfreeze

Bugfixes

- Also pass `--no-input` to pip when it is installed in the target venv. ([158](https://github.com/sbidoul/pip-deepfreeze/issues/158))
- Ensure we don't use setuptools>=71 ([159](https://github.com/sbidoul/pip-deepfreeze/pull/159))
- Force refresh of project metadata when using `uv` ([160](https://github.com/sbidoul/pip-deepfreeze/pull/160))

Features

- Use ``uv`` for freeze and uninstall operations too when ``uvpip`` has been selected. ([156](https://github.com/sbidoul/pip-deepfreeze/issues/156))
- Don't do the direct url fixup optimization hack when ``uvpip`` has been selected. ([156](https://github.com/sbidoul/pip-deepfreeze/issues/156))

Features

- Add support for pre-sync commands. ([152](https://github.com/sbidoul/pip-deepfreeze/issues/152))

Features

- Pass `--no-input` to pip commands, to avoid silently blocking on user input. ([131](https://github.com/sbidoul/pip-deepfreeze/issues/131))
- Use `uv`'s `--python` option to select the interpreter, instead of passing it as a
`VIRTUAL_ENV` environment variable. This is more explicit and hopefully more resilient
to changes in `uv`'s Python detection logic. ([145](https://github.com/sbidoul/pip-deepfreeze/issues/145))

Deprecations and Removals

- Change `--installer=uv` to `--installer=uvpip`. This is a breaking
change that we do while this is young, to avoid possible confusion in
the future with other `uv` install mechanisms that are on their
roadmap.
([\144](https://github.com/sbidoul/pip-deepfreeze/issues/144))

Features

- Allow to declare minimum pip-deepfreeze version in `pyproject.toml`.
`pip-deepfreeze` verifies its version according to
`tool.pip-deepfreeze.min_version`, so a project can ensure all
contributors have the minmum required version.
([\95](https://github.com/sbidoul/pip-deepfreeze/issues/95))
- Always install `uv` as a dependency. Consequently, the `uv` extra is
removed.
([\143](https://github.com/sbidoul/pip-deepfreeze/issues/143))