Repository navigation
Remove vulnerable filelock from development dependencies - #41
Merged
Merged
Conversation
This file contains hidden or 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
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.
The Python 3.10 development lock retained filelock 4.1.0, affected by Dependabot alerts #113–118. Patched filelock releases require Python >=3.11. Keep Python 3.10 runtime and test support, but run optional pre-commit tooling on Python >=3.11 and require filelock >=4.2.1 there; the lock resolves 4.2.4 and removes 4.1.0 entirely.
Validation: poetry check --lock passed; offline protocol/serialization suites: 116 passed, 1 expected failure. Full CI matrix covers Python 3.10–3.14. Full local Docker-backed suite is still running.