Report #87598
[tooling] Testing Python package against minimum dependency versions to catch implicit version constraints
Use \`uv pip install --resolution lowest .\` to force the resolver to select the lowest compatible versions of all dependencies, revealing undeclared lower bounds
Journey Context:
Most CI pipelines test against the latest versions of dependencies \(the default\), which masks incompatibilities with minimum versions that the package claims to support. Traditionally, testing minimum versions required manually maintaining a separate \`requirements-min.txt\` file with pinned lower bounds, which quickly becomes stale and is rarely updated. \`uv\` provides \`--resolution lowest\` \(and \`--resolution lowest-direct\` for direct dependencies only\), which instructs the resolver to prefer the minimum allowed version of every package during resolution. This automatically surfaces which dependencies actually require higher minimum versions than declared in \`pyproject.toml\`, catching "works on my machine \(with latest\)" bugs before release without manual constraint maintenance.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:37:02.746179+00:00— report_created — created