Bump filelock from 3.32.0 to 3.32.2

[dependabot]

Bumps filelock from 3.32.0 to 3.32.2.

Release notes

Sourced from filelock's releases.

3.32.2

What's Changed

• Fix test failures on NetBSD (#689) by @​gaborbernat in tox-dev/filelock#693
• 🧪 test(soft-rw): deflake writer phase-2 peer-marker test by @​gaborbernat in tox-dev/filelock#694
• hand back the claim when a heartbeat thread fails to start by @​dxbjavid in tox-dev/filelock#691
• 🧪 test(unix): deflake sticky-bit concurrent-unlink on graalpy by @​gaborbernat in tox-dev/filelock#695

Full Changelog: tox-dev/filelock@3.32.1...3.32.2

Changelog

Sourced from filelock's changelog.

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

.. towncrier-draft-entries:: Unreleased

.. towncrier release notes start

---

3.32.2 (2026-07-29)

---

• A SoftReadWriteLock or SoftFileLease 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:691

---

3.32.1 (2026-07-26)

---

• Canceling an AsyncSoftReadWriteLock acquire now releases the claim instead of leaking a marker whose heartbeat wedges every contender. :pr:686

---

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

---

... (truncated)

Commits

• 9a6cc43 Release 3.32.2
• 56879c7 🧪 test(unix): deflake sticky-bit concurrent-unlink on graalpy (#695)
• ecf5be0 hand back the claim when a heartbeat thread fails to start (#691)
• ee70d2e 🧪 test(soft-rw): deflake writer phase-2 peer-marker test (#694)
• 1eb14dd Fix test failures on NetBSD (#689) (#693)
• d81e859 build(deps): bump astral-sh/setup-uv from 8.3.2 to 9.0.0 (#692)
• 6fbc905 [pre-commit.ci] pre-commit autoupdate (#690)
• 34d1c38 build(deps): bump pypa/gh-action-pypi-publish from 1.14.0 to 1.14.1 (#688)
• bf13ec7 Release 3.32.1
• 887f114 build(deps): bump actions/checkout from 7.0.0 to 7.0.1 (#687)
• 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 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)

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	28.59s
✅ JSON	prettier	7	0	0	0	1.23s
✅ JSON	v8r	7		0	0	3.55s
✅ MARKDOWN	markdownlint	68	0	0	0	2.1s
✅ MARKDOWN	markdown-table-formatter	68	0	0	0	0.68s
✅ PYTHON	black	1782	44	0	0	96.14s
✅ PYTHON	isort	1782	67	0	0	2.82s
✅ REPOSITORY	betterleaks	yes		no	no	1.91s
✅ REPOSITORY	checkov	yes		no	no	60.86s
✅ REPOSITORY	gitleaks	yes		no	no	13.41s
✅ REPOSITORY	git_diff	yes		no	no	0.27s
✅ REPOSITORY	secretlint	yes		no	no	89.2s
✅ REPOSITORY	syft	yes		no	no	5.62s
✅ REPOSITORY	trivy-sbom	yes		no	no	7.32s
✅ REPOSITORY	trufflehog	yes		no	no	33.14s
✅ YAML	prettier	11	0	0	0	0.88s
✅ YAML	v8r	11		0	0	11.56s
✅ YAML	yamllint	11		0	0	0.68s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.6.0 --custom-flavor-setup --custom-flavor-linters PYTHON_BLACK,PYTHON_ISORT,COPYPASTE_JSCPD,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.