chore(tox): Use lock runners for more tests #1447
Merged
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.
While releasing 5.3.3, various checks had stopped passing because the dependencies had been updated. This expands the use of lockfiles to more environments to reduce the scope for dependency rot in maintenance branches.
In the main branch, this sets dependabot to update the uv lockfile, which lets us address changes in dependencies in the PR that updates them, rather than when CI starts spontaneously failing. For maintenance branches, we don't need to update lockfiles, we just need the environment to keep working.