dependabot[bot] opened a new pull request, #76612: URL: https://github.com/apache/airflow/pull/76612
Bumps the 3-4-uv-dependency-updates group in /dev/breeze with 1 update: [filelock](https://github.com/tox-dev/filelock). Updates `filelock` from 4.2.6 to 4.2.7 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/filelock/releases";>filelock's releases</a>.</em></p> <blockquote> <h2>4.2.7</h2> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> <h3>Bug fixes</h3> <ul> <li>A <code>SoftFileLease</code> reclaims a dead holder's lease marker even when that holder published another <code>lease_duration</code>. It used to raise <code>LeaseSettingsMismatch</code> on every attempt instead, so after a holder crashed and its peers restarted with a changed duration the lock stayed wedged until <code>force_break()</code>. A live holder with another duration still raises (<a href="https://redirect.github.com/tox-dev/filelock/pull/900";>#900</a>) by <a href="https://github.com/dxbjavid";><code>@dxbjavid</code></a> and <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> </ul> <p><a href="https://pypi.org/project/filelock/4.2.7/";>PyPI release</a></p> <p><a href="https://github.com/tox-dev/filelock/compare/4.2.6...4.2.7";>Full Changelog</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/filelock/blob/main/docs/changelog.rst";>filelock's changelog</a>.</em></p> <blockquote> <p>########### Changelog ###########</p> <p>.. towncrier-draft-entries:: Unreleased</p> <p>.. towncrier release notes start</p> <p>.. _release-4-2-9:</p> <hr /> <p>4.2.9 (2026-11-04)</p> <hr /> <p>.. _release-4-2-9-fixed:</p> <h1>Fixed</h1> <ul> <li>:class:<code>~filelock.ReadWriteLock</code>, :class:<code>~filelock.SoftReadWriteLock</code> and their async wrappers now raise :class:<code>TypeError</code> for a <em>blocking</em> that is not a :class:<code>bool</code>, in the constructor and on acquire, as :class:<code>~filelock.FileLock</code> already does. Before, <code>blocking=0</code> waited out the full timeout on a contended :class:<code>~filelock.ReadWriteLock</code> while <code>blocking=False</code> failed at once, and a truthy value such as <code>"false"</code> turned a single attempt into a blocking wait (:pr:<code>908</code>) by :user:<code>abhishekcpp007</code> and :user:<code>gaborbernat</code>.</li> </ul> <p>.. _release-4-2-8:</p> <hr /> <p>4.2.8 (2026-11-04)</p> <hr /> <p>.. _release-4-2-8-documentation:</p> <h1>Documentation</h1> <ul> <li>Clarify the platform-specific locking primitive and range used by descriptor locks, and correct the guidance on interoperating with byte-range lock protocols such as conda's repodata lock (:pr:<code>905</code>) by :user:<code>boyfeiyu</code>.</li> </ul> <p>.. _release-4-2-7:</p> <hr /> <p>4.2.7 (2026-11-02)</p> <hr /> <p>.. _release-4-2-7-fixed:</p> <h1>Fixed</h1> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tox-dev/filelock/commit/5fd486b3a45864d7c39081bd3d2905321c7f6640";><code>5fd486b</code></a> release 4.2.7</li> <li><a href="https://github.com/tox-dev/filelock/commit/ff847352b212753800ee74494ad67e78673dcfdf";><code>ff84735</code></a> 🐛 fix(lease): reclaim dead holders after duration changes (<a href="https://redirect.github.com/tox-dev/filelock/issues/900";>#900</a>)</li> <li>See full diff in <a href="https://github.com/tox-dev/filelock/compare/4.2.6...4.2.7";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
