Repository navigation
Bump filelock from 3.20.3 to 4.2.1 - #125
Conversation
Bumps [filelock](https://github.com/tox-dev/filelock) from 3.20.3 to 4.2.1. - [Release notes](https://github.com/tox-dev/filelock/releases) - [Changelog](https://github.com/tox-dev/filelock/blob/main/docs/changelog.rst) - [Commits](tox-dev/filelock@3.20.3...4.2.1) --- updated-dependencies: - dependency-name: filelock dependency-version: 4.2.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
d33bs
left a comment
There was a problem hiding this comment.
Major-bump review completed: filelock is only a transitive dependency of torch (zero direct imports in src/tests/pyproject); grep of codebase confirms no direct usage. Reviewed upstream release notes for filelock 4.0.0-4.2.1: the only breaking change (SoftReadWriteLock on-disk generation-log protocol) is confined to an advanced API torch does not use (torch only uses the basic FileLock). Full CI matrix green (12 jobs, py3.10-3.14 x macOS/ubuntu), pre-commit and benchmark canary pass, lockfile-only diff, mergeStateStatus CLEAN. Approving.
Bumps filelock from 3.20.3 to 4.2.1.
Release notes
Sourced from filelock's releases.
... (truncated)
Changelog
Sourced from filelock's changelog.
... (truncated)
Commits
60331bbRelease 4.2.1834bf13🧪 test(soft): skip Unix pin test on Windows9d15e38fix(soft-rw): isolate subclass singleton registries (#855)e1e825b🐛 fix(open): keep lock files intact, honor deadlines and mode (#835)5e3f2ec🐛 fix(read-write): keep SQLite off shared names, bound schema (#834)bfa066d🐛 fix(strict): keep claim directories private to the lock (#839)977d2c3🐛 fix(soft): wait on an empty marker instead of evicting (#846)740ff66🐛 fix(soft): break stale markers without emptying the lock path (#843)86c6d5f🐛 fix(async): honor cancellation and per-thread gates (#844)eeceaa8🐛 fix(soft): keep live holders when owner identity differs (#836)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.