Repository navigation
chore(deps): dependency sweep — in-range freshening - #2360
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2360 +/- ##
==========================================
+ Coverage 94.11% 94.13% +0.02%
==========================================
Files 184 184
Lines 13647 13647
==========================================
+ Hits 12844 12847 +3
+ Misses 803 800 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
vdusek
approved these changes
Oct 28, 2026
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.
Summary
Dependency sweep — in-range freshening (all within existing ranges):
cachetools7.2.4 → 7.2.6curl-cffi0.16.3 → 0.17.0grpcio1.84.1 → 1.85.0jsonpath-ng1.13.0 → 1.14.0logfire-api5.3.0 → 5.4.0lxml-html-clean0.4.5 → 0.4.6openai3.37.0 → 3.39.0pytest-asyncio1.4.0 → 1.4.1ruff0.17.2 → 0.17.3ty0.0.91 → 0.0.92✅ Dismissed (don't apply to our usage)
All 6 open alerts are
filelockCVEs in theSoftFileLock/MarkerSoftFileLock/SoftFileLease/ReadWriteLock/AsyncReadWriteLockclasses. crawlee-python only imports the plainfilelock.FileLock(native OSflock/LockFileExlock), and only intests/e2e/conftest.pyto serialize the wheel build in a private pytest tmp dir — none of the vulnerable classes are ever instantiated.filelock(high) — not_used: vuln is inReadWriteLock's SQLite backend; we only useFileLock. (alert #227)filelock(medium) — not_used: vuln is inSoftFileLock's stale-break restore; we only useFileLock. (alert #228)filelock(medium) — not_used: vuln is inSoftFileLock's marker-eviction timing; we only useFileLock. (alert #229)filelock(low) — not_used: Windows-only vuln inSoftFileLock's oplock wait; we only useFileLock. (alert #230)filelock(low) — not_used: Windows-only vuln inReadWriteLock's SQLite side files; we only useFileLock. (alert #231)filelock(medium) — not_used: vuln is inReadWriteLock's hard-link route; we only useFileLock. (alert #232)Note: even disregarding usage,
filelock>4.1.0 requires Python ≥3.11, and this repo supports Python ≥3.10, so no patched version (4.2.1+) is installable on the py3.10 line anyway — moot here since the vulnerable code path isn't used.🤖 Generated with Claude Code