dependabot[bot] opened a new pull request, #75527: URL: https://github.com/apache/airflow/pull/75527
Bumps the uv-security-updates group with 1 update in the /dev/breeze directory: [filelock](https://github.com/tox-dev/py-filelock). Updates `filelock` from 4.2.0 to 4.2.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/py-filelock/releases";>filelock's releases</a>.</em></p> <blockquote> <h2>4.2.1</h2> <ul> <li>On a singleton wrapper, <code>close></code> and <code>close></code> end only the holds that tasks acquired through that wrapper. A reader that arrives during <code>close()</code> gets the closed error instead of joining the ending hold. After synchronous code closes or force-releases the shared lock, the wrappers refuse to admit readers into the ended hold, and <code>close()</code> on such a wrapper returns. Closing one wrapper no longer ends a task's nested hold taken through another wrapper on the same path. <a href="https://redirect.github.com/tox-dev/py-filelock/issues/832";>#832</a></li> <li><code>ReadWriteLock</code> locks again after a <code>release()</code> that an exception from a signal handler interrupted. The async read-write wrappers stop admitting readers into such a level. The async read-write locks forget a hold whose backend release failed after the backend let go, and they free the memory of each acquire that times out or is canceled. <code>AsyncFileLock</code> returns from <code>release()</code> after a few hundred acquires gave up behind a waiting one. An exception from a signal handler delivered while an <code>AsyncFileLock</code> call joins its queue no longer blocks every later call on that lock. <a href="https://redirect.github.com/tox-dev/py-filelock/issues/833";>#833</a></li> <li>Fix <code>ReadWriteLock</code> acting on <code>-journal</code>, <code>-wal</code> or <code>-shm</code> files another process puts beside its database: a write could land in another file, a reader could get in beside a writer, and an acquire could fail. SQLite now opens the database by name only in a directory no other account can write, and through a private hard link elsewhere. On Windows the directory's access control list decides. Where hard links are unavailable, keep the database in a directory other accounts cannot write, such as one under <code>%LOCALAPPDATA%</code>. The lock removes link directories through a checked descriptor rather than by name, reads a link directory's name only when the locking account owns it, and leaves alone a directory with other content renamed onto a link directory's name. A database whose schema takes more than a few kilobytes to load raises <code>ValueError</code> instead of running past the acquire timeout. <a href="https://redirect.github.com/tox-dev/py-filelock/issues/834";>#834</a></li> <li>Fix five bugs in opening the lock file. <code>UnixFileLock</code> no longer truncates a file it did not create, such as one renamed to the lock path, and no longer applies <code>mode</code> to it. An <code>on_acquired</code> hook that writes holder metadata now truncates the file itself. A lease (Linux) or an oplock (Windows) on the lock file or a soft lock's marker no longer holds <code>acquire()</code> past its <code>timeout</code> or <code>blocking=False</code>, and an oplock no longer holds <code>release()</code>; <code>ReadWriteLock</code> on Windows waits for its <code>timeout</code> and raises <code>Timeout</code>. On Windows, a <code>mode</code> without group and other bits, such as <code>0o600</code>, now creates the lock file with an owner-only permission list; the <code>ReadWriteLock</code> database gets the same. The soft locks' writability check no longer follows a symlink swapped in at the lock path. On a filesystem without <code>flock</code>, a contender from another account now waits on a marker it cannot write instead of raising <code>PermissionError</code>. <a href="https://redirect.github.com/tox-dev/py-filelock/issues/835";>#835</a></li> <li>Fix <code>SoftFileLock</code>, <code>MarkerSoftFileLock</code> and <code>SoftFileLease</code> removing a live holder's marker in three cases: the holder and the contender run in Linux time namespaces with different boottime offsets; only one of them can read the boot id; a process other than the owner rewrote the marker. Soft markers no longer carry group or other write bits. A process name containing a carriage return or another line separator no longer makes the stale check raise <code>ValueError</code>. When <code>/proc/self/ns/time</code> exists but cannot be read, the stale check no longer compares start times and keeps the marker. <a href="https://redirect.github.com/tox-dev/py-filelock/issues/836";>#836</a></li> <li>The async read-write locks record their hold under a task owner, so synchronous code on the executor thread that took the hold can no longer re-enter or release it. <code>AsyncSoftReadWriteLock</code> gives back one level on release, so synchronous readers of a shared singleton keep theirs. <code>SoftReadWriteLock</code> tracks read levels per thread: <code>release()</code> from a thread that holds none raises <code>RuntimeError</code>. After its heartbeat recorded a lost hold, it refuses new acquires until that hold is released. <a href="https://redirect.github.com/tox-dev/py-filelock/issues/838";>#838</a></li> <li><code>StrictSoftFileLock</code> creates <code><path>.filelock</code> and its <code>claims</code> directory with the lock's <code>mode</code> and sets the sticky bit (a directory flag that lets only a file's owner remove it) on both. On the next acquisition it narrows a directory it owns that an earlier release created wider; it leaves a directory of another account as it is, so remove such leftovers by hand. It reaches <code>claims</code> through a descriptor opened without following symlinks; on Windows it holds both directories open and refuses a junction (a directory that points at another directory). Under a sticky parent such as <code>/tmp</code> it refuses a coordination directory of another account, as <code>SoftReadWriteLock</code> does for <code><path>.rw</code>. One read grace now covers a whole claim scan, a failed claim cleanup no longer leaves the sentinel descriptor open, and a non-regular node at a sentinel private-record name raises <code>SoftFileLockProtocolError</code>. On Windows, contenders read claims without blocking their owner's unlink. <a href="https://redirect.github.com/tox-dev/py-filelock/issues/839";>#839</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </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> <hr /> <p>4.2.4 (2026-10-19)</p> <hr /> <ul> <li>Keep GitHub Release notes free of extra blank lines while retaining the PyPI and version comparison links. :pr:<code>863</code></li> </ul> <hr /> <p>4.2.3 (2026-10-19)</p> <hr /> <ul> <li>Creating a lock on a Python 3.15 interpreter without <code>types.LazyImportType</code> no longer triggers <code>AttributeError</code> at exit. :pr:<code>860</code></li> <li>Handle <code>EFTYPE</code> when a no-follow open refuses a symlink in a soft reader/writer lock's protocol tree, so heartbeat reports lost ownership rather than a transient refresh error.</li> </ul> <hr /> <p>4.2.2 (2026-10-18)</p> <hr /> <ul> <li>Fix a lock on a relative path that stayed held after a later <code>with lock:</code> ended, when an earlier <code>acquire()</code> had failed because the working directory no longer exists. That call still raises :class:<code>FileNotFoundError</code>, and it now leaves the lock's hold count unchanged. :pr:<code>856</code></li> </ul> <hr /> <p>4.2.1 (2026-10-17)</p> <hr /> <ul> <li>On a singleton wrapper, :meth:<code>AsyncReadWriteLock.close() <filelock.AsyncReadWriteLock.close></code> and :meth:<code>AsyncSoftReadWriteLock.close() <filelock.AsyncSoftReadWriteLock.close></code> end only the holds that tasks acquired through that wrapper. A reader that arrives during <code>close()</code> gets the closed error instead of joining the ending hold. After synchronous code closes or force-releases the shared lock, the wrappers refuse to admit readers into the ended hold, and <code>close()</code> on such a wrapper returns. Closing one wrapper no longer ends a task's nested hold taken through another wrapper on the same path. :pr:<code>832</code></li> <li>:class:<code>~filelock.ReadWriteLock</code> locks again after a <code>release()</code> that an exception from a signal handler interrupted. The async read-write wrappers stop admitting readers into such a level. The async read-write locks forget a hold whose backend release failed after the backend let go, and they free the memory of each acquire that times out or is canceled. :class:<code>~filelock.AsyncFileLock</code> returns from <code>release()</code> after a few hundred acquires gave up behind a waiting one. An exception from a signal handler delivered while an :class:<code>~filelock.AsyncFileLock</code> call joins its queue no longer blocks every later call on that lock. :pr:<code>833</code></li> <li>Fix :class:<code>~filelock.ReadWriteLock</code> acting on <code>-journal</code>, <code>-wal</code> or <code>-shm</code> files another process puts beside its database: a write could land in another file, a reader could get in beside a writer, and an acquire could fail. SQLite now opens the database by name only in a directory no other account can write, and through a private hard link elsewhere. On Windows the directory's access control list decides. Where hard links are unavailable, keep the database</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tox-dev/filelock/commit/60331bb89f325020b48bc51bde904c6446384e4a";><code>60331bb</code></a> Release 4.2.1</li> <li><a href="https://github.com/tox-dev/filelock/commit/834bf130760b2672615510f0288af1e1dcb7467c";><code>834bf13</code></a> ๐งช test(soft): skip Unix pin test on Windows</li> <li><a href="https://github.com/tox-dev/filelock/commit/9d15e38e50f7dd7f318e912d3bcd5f7697c3f8a1";><code>9d15e38</code></a> fix(soft-rw): isolate subclass singleton registries (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/855";>#855</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a";><code>e1e825b</code></a> ๐ fix(open): keep lock files intact, honor deadlines and mode (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/835";>#835</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d";><code>5e3f2ec</code></a> ๐ fix(read-write): keep SQLite off shared names, bound schema (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/834";>#834</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03";><code>bfa066d</code></a> ๐ fix(strict): keep claim directories private to the lock (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/839";>#839</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/977d2c3990d2d7ccc53abefe6434fa403c35bc70";><code>977d2c3</code></a> ๐ fix(soft): wait on an empty marker instead of evicting (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/846";>#846</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/740ff666b62a88496c8d7394e4e6230605e4d62b";><code>740ff66</code></a> ๐ fix(soft): break stale markers without emptying the lock path (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/843";>#843</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/86c6d5fb9c23bbcc9f20ab7eda0d625305549b64";><code>86c6d5f</code></a> ๐ fix(async): honor cancellation and per-thread gates (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/844";>#844</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/eeceaa846cbe4df72718d94c8371ca1ab8f5b3cc";><code>eeceaa8</code></a> ๐ fix(soft): keep live holders when owner identity differs (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/836";>#836</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tox-dev/py-filelock/compare/4.2.0...4.2.1";>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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/airflow/network/alerts). </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]
