-
Notifications
You must be signed in to change notification settings - Fork 602
[MEDIUM] Upgrade python-filelock to 3.20.1 for CVE-2025-68146 #15376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MEDIUM] Upgrade python-filelock to 3.20.1 for CVE-2025-68146 #15376
Conversation
|
Buddy Build : 1011081 Buddy build results are successful |
|
Changes looks fine, buddy build passes. |
kgodara912
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please keep the separation of test requires if they are not causing build failures.
|
Buddy build after recent changes. |
kgodara912
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Buddy build is successful. The module is a small python module with ~10 files. There is no major change while comparing the code between these two versions and they are compatible. Only change was minor refactoring and asyncio support. LGTM.
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
What does the PR accomplish, why was it needed?
Upgrade python-filelock to 3.20.1 for CVE-2025-68146
Duplicate of #15346
Change Log
Does this affect the toolchain?
NO
Links to CVEs
Test Methodology
Build and Test is successful
