You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up from #2791 and #2774, we should add a step to the test workflow which runs the test suite again but with the lowest supported dependencies installed. Unfortunately there doesn't really seem to be good tooling for this (short of https://github.com/ffy00/python-resolver#mindeps-cli) so this may be blocked until such tooling exists or we could take the cheap to implement / more expensive down the road route of defining a constraints file that manually pins the dependencies to the lowest versions supported.
We could run diff-shades/primer against the minimum dependencies but I'm wary of the CI time increases. Especially as it's unlikely an older version of a dependency would cause a subtle issue with formatting (given the core formatting logic is all our own) that these sorts of jobs discover.
The text was updated successfully, but these errors were encountered:
Follow-up from #2791 and #2774, we should add a step to the test workflow which runs the test suite again but with the lowest supported dependencies installed. Unfortunately there doesn't really seem to be good tooling for this (short of https://github.com/ffy00/python-resolver#mindeps-cli) so this may be blocked until such tooling exists or we could take the cheap to implement / more expensive down the road route of defining a constraints file that manually pins the dependencies to the lowest versions supported.
We could run diff-shades/primer against the minimum dependencies but I'm wary of the CI time increases. Especially as it's unlikely an older version of a dependency would cause a subtle issue with formatting (given the core formatting logic is all our own) that these sorts of jobs discover.
The text was updated successfully, but these errors were encountered: