Bump the uv-dependency-updates group in /dev/breeze with 2 updates

[dependabot]

Bumps the uv-dependency-updates group in /dev/breeze with 2 updates: filelock and gitpython.

Updates filelock from 3.31.0 to 3.31.1

Release notes

Sourced from filelock's releases.

3.31.1

What's Changed

• ♻️ refactor(coverage): key exclusions on probed capability by @​gaborbernat in tox-dev/filelock#679
• scope a lease's claim to the context that acquired it by @​dxbjavid in tox-dev/filelock#680

Full Changelog: tox-dev/filelock@3.31.0...3.31.1

Changelog

Sourced from filelock's changelog.

########### Changelog ###########

.. towncrier-draft-entries:: Unreleased

.. towncrier release notes start

---

3.32.0 (2026-07-21)

---

• SoftReadWriteLock closes the directory handle it opens to scan for readers as soon as a scan stops early, rather than holding it until the generator is collected. :pr:685
• Declare support for Python 3.15 and run the test suite against it and its free-threaded build, both currently in beta. :pr:683
• The source distribution ships the capability probes the tests import, and reading one no longer needs coverage installed, so the suite runs from an unpacked sdist instead of failing on a missing coverage_pragmas. :pr:685

---

3.31.2 (2026-07-21)

---

• filelock imports again on runtimes whose errno omits ENOTSUP, such as GraalPy, where importing the package raised ImportError. It probes the code instead, preferring ENOTSUP, falling back to EOPNOTSUPP where that name is absent, and dropping to ENOSYS/EXDEV where neither exists. Platforms defining ENOTSUP keep their behavior. :pr:681

---

3.31.1 (2026-07-20)

---

• A SoftFileLease acquired on one thread keeps its claim when another thread fails to acquire the same lease object, so its heartbeat carries on refreshing the marker instead of being torn down and letting a peer take the live claim. :pr:680

---

3.31.0 (2026-07-18)

---

• Support Termux/Android, whose CPython ships without os.link and reports sys.platform == "android". import filelock and both FileLock and SoftFileLock now work there, StrictSoftFileLock reports its missing hard-link support only when acquired, and process liveness reads /proc on Android instead of PID-only checks. :pr:678
• StrictSoftFileLock no longer lets two processes hold the lock at once under heavy contention. A holder now keeps its intent claim for the whole hold, so a contender whose directory scan races the holder's freshly linked claim can no longer miss it and win alongside it. A held lock now exposes both an intent and a held claim. :pr:678

---

3.30.3 (2026-07-17)

---

• AsyncFileLock and AsyncSoftFileLock no longer raise a deadlock RuntimeError when a different asyncio task

... (truncated)

Commits

• c1b2e6f Release 3.31.1
• 9fd7de5 scope a lease's claim to the context that acquired it (#680)
• 2b3ad2c ♻️ refactor(coverage): key exclusions on probed capability (#679)
• See full diff in compare view

Updates gitpython from 3.1.52 to 3.1.53

Release notes

Sourced from gitpython's releases.

3.1.53 - Security

What's Changed

• feat(submodule): add deinit method to Submodule (#2014) by @​mvanhorn in gitpython-developers/GitPython#2129
• typing: introduce sensible basedpyright defaults by @​Byron in gitpython-developers/GitPython#2174
• fix: make submodule.update() after submodule.deinit() work by @​Byron in gitpython-developers/GitPython#2175
• Fix commit hooks respecting core.hooksPath by @​Siesta0217 in gitpython-developers/GitPython#2159
• fix: validate config section delimiters by @​Byron in gitpython-developers/GitPython#2176

New Contributors

• @​Siesta0217 made their first contribution in gitpython-developers/GitPython#2159

Full Changelog: gitpython-developers/GitPython@3.1.52...3.1.53

Commits

• faf3c09 prepare for security fix
• 6a5eb6a Merge pull request #2176 from gitpython-developers/fix-config-injection
• 1ed1b92 fix: validate config section delimiters
• 354eb2f Merge pull request #2159 from Siesta0217/fix-core-hooks-path-commit-hooks
• 9bc287a Address review feedback about hook resolution
• 406b98e fix: respect core.hooksPath for commit hooks
• 5bc2560 upate contributing guide to avoid agent impersonation
• 15527ef Merge pull request #2175 from gitpython-developers/submodule-deinit-fix
• b9d82c0 fix: make submodule.update() after submodule.deinit() work
• f89e18c Merge pull request #2174 from gitpython-developers/basedpyright
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker d31eff5 v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.