Skip to content

[pull] master from aio-libs:master - #749

Merged
pull[bot] merged 1 commit into
tj-python:masterfrom
aio-libs:master
Sep 4, 2026
Merged

[pull] master from aio-libs:master#749
pull[bot] merged 1 commit into
tj-python:masterfrom
aio-libs:master

Conversation

@pull

@pull pull Bot commented Sep 4, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

Bumps [filelock](https://github.com/tox-dev/py-filelock) from 3.32.4 to
3.32.5.
<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>3.32.5</h2>
<!-- raw HTML omitted -->
<h2>What's Changed</h2>
<ul>
<li>🧪 test(fork): report where a stalled fork stops by <a
href="https://github.com/gaborbernat"><code>@​gaborbernat</code></a> in
<a
href="https://redirect.github.com/tox-dev/filelock/pull/715">tox-dev/filelock#715</a></li>
<li>📝 docs: say that mode is read-only in the thread-local section by <a
href="https://github.com/Gares95"><code>@​Gares95</code></a> in <a
href="https://redirect.github.com/tox-dev/filelock/pull/716">tox-dev/filelock#716</a></li>
<li>🐛 fix(lease): clear token after failed acquire by <a
href="https://github.com/lprnmns"><code>@​lprnmns</code></a> in <a
href="https://redirect.github.com/tox-dev/filelock/pull/721">tox-dev/filelock#721</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/lprnmns"><code>@​lprnmns</code></a> made
their first contribution in <a
href="https://redirect.github.com/tox-dev/filelock/pull/721">tox-dev/filelock#721</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/tox-dev/filelock/compare/3.32.4...3.32.5">https://github.com/tox-dev/filelock/compare/3.32.4...3.32.5</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>
<hr />
<p>3.32.5 (2026-08-31)</p>
<hr />
<ul>
<li><code>SoftFileLease.token</code> and
<code>AsyncSoftFileLease.token</code> now read <code>None</code> after a
failed acquisition, so a contender
turned away by a live holder no longer reports a token for a claim it
never published. :pr:<code>721</code></li>
<li>Document that <code>mode</code> has no setter: unlike
<code>poll_interval</code>, <code>timeout</code>, <code>blocking</code>
and <code>lifetime</code>, it is fixed at construction and
<code>lock.mode = ...</code> raises <code>AttributeError</code>.
:pr:<code>716</code></li>
</ul>
<hr />
<p>3.32.4 (2026-08-23)</p>
<hr />
<ul>
<li><code>StrictSoftFileLock</code> always retries a claim read whose
first attempt reports the claim as pending, so a first read
that itself outlasts the retry grace no longer fails closed on a claim
it could have read. :pr:<code>705</code></li>
<li><code>WindowsFileLock</code> waits out a transient
<code>STATUS_ACCESS_DENIED</code> from <code>NtCreateFile</code> for up
to half a second
before raising <code>PermissionError</code>, since a peer unlinking the
lock file as it releases can answer that for a moment; a
real denial still fails fast. :pr:<code>705</code></li>
<li>Every lock class now escapes the hostname it publishes, so a host
whose <code>socket.gethostname()</code> carries a space, a
newline or a byte outside UTF-8 no longer writes a marker it reads back
as malformed. Such a host used to lose a held
<code>SoftReadWriteLock</code> read slot to a peer and could not take a
write slot or a <code>StrictSoftFileLock</code> at all.
:pr:<code>709</code></li>
</ul>
<hr />
<p>3.32.3 (2026-08-13)</p>
<hr />
<ul>
<li>The fork-safety audit hook no longer prints <code>Exception ignored
in audit hook</code> with a <code>TypeError</code> when an audit
event fires during interpreter shutdown, after CPython has already
cleared the module globals. :pr:<code>701</code></li>
</ul>
<hr />
<p>3.32.2 (2026-07-29)</p>
<hr />
<ul>
<li>A <code>SoftReadWriteLock</code> or <code>SoftFileLease</code>
acquire whose heartbeat thread fails to start now unlinks its marker and
hands the claim back, instead of leaving an unrefreshed marker a peer
takes while the caller believes it still holds
the lock. :pr:<code>691</code></li>
</ul>
<hr />
<p>3.32.1 (2026-07-26)</p>
<hr />
<ul>
<li>Canceling an <code>AsyncSoftReadWriteLock</code> acquire now
releases the claim instead of leaking a marker whose heartbeat
wedges every contender. :pr:<code>686</code></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/1585dfef9355a5c77d4a9498cc34d3a98056fdb9"><code>1585dfe</code></a>
Release 3.32.5</li>
<li><a
href="https://github.com/tox-dev/filelock/commit/00177c32686e60bc5ef9875b5841867ea08d4558"><code>00177c3</code></a>
🐛 fix(lease): clear token after failed acquire (<a
href="https://redirect.github.com/tox-dev/py-filelock/issues/721">#721</a>)</li>
<li><a
href="https://github.com/tox-dev/filelock/commit/5aeb9b6a5fe1e86dcb1c44a927aefffd607b17b0"><code>5aeb9b6</code></a>
📝 docs: say that mode is read-only in the thread-local section (<a
href="https://redirect.github.com/tox-dev/py-filelock/issues/716">#716</a>)</li>
<li><a
href="https://github.com/tox-dev/filelock/commit/2634dd1dcc597b319770df027491f16d07662952"><code>2634dd1</code></a>
[pre-commit.ci] pre-commit autoupdate (<a
href="https://redirect.github.com/tox-dev/py-filelock/issues/720">#720</a>)</li>
<li><a
href="https://github.com/tox-dev/filelock/commit/37dccf0276f6db1520db9e3482fdf0446c14276e"><code>37dccf0</code></a>
🧪 test(fork): report where a stalled fork stops (<a
href="https://redirect.github.com/tox-dev/py-filelock/issues/715">#715</a>)</li>
<li>See full diff in <a
href="https://github.com/tox-dev/py-filelock/compare/3.32.4...3.32.5">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=filelock&package-manager=pip&previous-version=3.32.4&new-version=3.32.5)](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 this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@pull pull Bot locked and limited conversation to collaborators Sep 4, 2026
@pull pull Bot added the ⤵️ pull label Sep 4, 2026
@pull
pull Bot merged commit 25522ad into tj-python:master Sep 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants