Allow later versions of filelock, psutil - unblock safety upgrades #642
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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. Similarly, psutil is also allowed later versions.
m000
changed the title
|
I am facing the same issue, this PR would fix it 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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