Skip to content

Upgrade python-filelock to 3.20.3 for CVE-2026-22701 [Medium]#15495

Merged
kgodara912 merged 2 commits into3.0-devfrom
cblmargh/python-filelock-upgrade-to-3.20.3-3.0-dev
Jan 21, 2026
Merged

Upgrade python-filelock to 3.20.3 for CVE-2026-22701 [Medium]#15495
kgodara912 merged 2 commits into3.0-devfrom
cblmargh/python-filelock-upgrade-to-3.20.3-3.0-dev

Conversation

@Kanishk-Bansal
Copy link
Contributor

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology

@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner January 13, 2026 09:14
@Kanishk-Bansal Kanishk-Bansal added the CVE-fixed-by-upgrade CVE fixed by package upgrade label Jan 13, 2026
@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Jan 13, 2026
@Kanishk-Bansal
Copy link
Contributor Author

@Kanishk-Bansal
Copy link
Contributor Author

Due to request status 500 - github REST API error
I had to manually create a PR

@mayankfz
Copy link
Contributor

minor version upgrade. Tests passing.

@mayankfz mayankfz added the ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review label Jan 20, 2026
@Kanishk-Bansal
Copy link
Contributor Author

/azurepipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Kanishk-Bansal
Copy link
Contributor Author

image

python-pytest-xdist is a known failure

Copy link
Contributor

@kgodara912 kgodara912 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor version upgrade for fixing CVE. Buddy build is successful. Changelog indicates only CVE and 3 other changes are fixed between these two releases. LGTM.

@kgodara912 kgodara912 merged commit 391c4df into 3.0-dev Jan 21, 2026
29 of 32 checks passed
@kgodara912 kgodara912 deleted the cblmargh/python-filelock-upgrade-to-3.20.3-3.0-dev branch January 21, 2026 06:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 CVE-fixed-by-upgrade CVE fixed by package upgrade Packaging ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants