Allow later versions of filelock, psutil - unblock safety upgrades #642
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.
Description
filelock dependency was introduced in July 4, 2024. However the pinned version was already outdated at that time.
This means that projects that had requirement files where filelock had already been upgraded to the latest are now stuck with safety 3.2.3 (the last one released without the new dependency).
The commit adding the dependency makes no case for pinning the specific version. So it looks more like an oversight, and allowing later versions should work.
Type of Change
Related Issues
Problem introduced by #544.
Testing
Checklist
Additional Notes