Bump the patch group with 2 updates

[dependabot]

Bumps the patch group with 2 updates: pylint and time-machine.

Updates pylint from 4.0.8 to 4.0.9

Release notes

Sourced from pylint's releases.

v4.0.9

What's new in Pylint 4.0.9?

Release date: 2026-09-23

Security Fixes

• Someone without access to the configuration or linted code, but with access to the cache directory (predictable PYLINT_HOME on a multi-user host) can no longer write a crafted pickle that will runs arbitrary code when pylint access its stat cache. The result cache is now stored as JSON instead of pickle, preventing code-execution. The workaround is upgrading or not pointing PYLINT_HOME to an untrusted, shared, or group-writable directory. The default value, ~/.cache/pylint, is writable only by the user running pylint. (CVE with the same information pending)

False Positives Fixed

• Fixed a false positive for no-self-use on a method that only uses self before a locally defined class (or other nested method), because the checker's could-be-a-function tracking state was not restored after visiting the nested method.

  Closes #3705

• Fix a false positive for :ref:not-callable when calling functions constructed with types.FunctionType or types.LambdaType.

  Closes #7500

• Fix a false positive for unnecessary-direct-lambda-call when a directly called lambda in a class body wraps a comprehension containing an assignment expression. PEP 572 makes that a SyntaxError without the lambda's scope, so following the message produced code that would not compile.

  Closes #9294

• Fix a false positive for :ref:unnecessary-ellipsis when an ellipsis is the sole body statement of a method defined on a Protocol.

  Closes #9319

• Fix a false positive for :ref:bad-exception-cause when the bases of the class being raised from cannot be inferred, such as an exception deriving from a C extension class. :ref:raising-non-exception and :ref:catching-non-exception already guard the same inherit_from_std_ex

... (truncated)

Commits

• 303703f Bump pylint to 4.0.9, update changelog (#11448)
• b342384 Fix block-scoped disable leaking into sibling elif/else blocks (#11429) (#11445)
• 58c87cf Store the results cache as JSON instead of pickle
• e3f4942 [Backport maintenance/4.0.x] Fix crash on failed attribute inference (#11443)
• faf47f9 [Backport maintenance/4.0.x] Fix false positive no-self-use when a method con...
• 20c7bb9 [Backport maintenance/4.0.x] Fix a crash in method-hidden for methods named a...
• 47e6757 [Backport maintenance/4.0.x] Fix bad-exception-cause false positive when the ...
• ae3ee53 [Backport maintenance/4.0.x] Fix not-callable false positive for types.Functi...
• 3e444be [Backport maintenance/4.0.x] Fix a crash in unnecessary-default-type-args for...
• 8f2dd4f [Backport maintenance/4.0.x] Fix declare-non-slot false positives for ClassVa...
• Additional commits viewable in compare view

Updates time-machine from 3.5.0 to 3.5.1

Changelog

Sourced from time-machine's changelog.

3.5.1 (2026-09-08)

• Only pass the compiler option -mno-omit-leaf-frame-pointer when the compiler supports it, checked with a tiny probe program. The option is unsupported outside of x86 and ARM64, so this fixes building from source on other architectures, like PowerPC, which failed since the option was added in version 3.3.0.

  PR [#692](https://github.com/adamchainz/time-machine/issues/692) <https://github.com/adamchainz/time-machine/pull/692>. Thanks to Colin Watson for pointing this out and linking to the workaround in Debian Bug [#1146407](https://github.com/adamchainz/time-machine/issues/1146407) <https://bugs.debian.org/1146407>.

• Fix the mocked datetime.date.today() and datetime.datetime.today() to be exact for all supported dates, like datetime.datetime.now(). Previously, they went through a floating-point timestamp, which could round the microseconds, or even the whole day, for dates far in the future.

  PR [#690](https://github.com/adamchainz/time-machine/issues/690) <https://github.com/adamchainz/time-machine/pull/690>__.

• Fix the class decorator to stop time travelling when tearDownClass() raises an exception, or when setUpClass() raises an exception not deriving from Exception, such as the skip outcome from pytest.skip(). Previously, time remained mocked for the rest of the process in these cases.

  PR [#678](https://github.com/adamchainz/time-machine/issues/678) <https://github.com/adamchainz/time-machine/pull/678>__.

• Fix Traveller.move_to() to keep the current timezone mocked when the given destination is unsupported. Previously, the timezone was restored before the destination was checked, leaving it unmocked whilst still time travelling.

  PR [#679](https://github.com/adamchainz/time-machine/issues/679) <https://github.com/adamchainz/time-machine/pull/679>__.

• Fix the time_machine pytest fixture to not try to stop a traveller that failed to start.

  PR [#680](https://github.com/adamchainz/time-machine/issues/680) <https://github.com/adamchainz/time-machine/pull/680>__.

• Fix the mocked time.strftime() to raise TypeError when passed None as its second argument, like the unmocked function, rather than treating it as the current time.

  PR [#681](https://github.com/adamchainz/time-machine/issues/681) <https://github.com/adamchainz/time-machine/pull/681>__.

• Fix the :ref:Migration CLI <migration-cli> to keep the rewritten imports on the same line when a freezegun import shares its line with other code, like if TYPE_CHECKING: from freezegun import freeze_time, FakeDate. Previously, the remaining from freezegun import FakeDate was moved to a new line, outside the block.

  PR [#682](https://github.com/adamchainz/time-machine/issues/682) <https://github.com/adamchainz/time-machine/pull/682>__.

• Extend the :ref:Migration CLI <migration-cli> to migrate uses of FrozenDateTimeFactory in string annotations, like freezer: "FrozenDateTimeFactory". Previously, the import was removed whilst such annotations were left referring to it.

  PR [#683](https://github.com/adamchainz/time-machine/issues/683) <https://github.com/adamchainz/time-machine/pull/683>__.

• Fix the :ref:Migration CLI <migration-cli> to not rename a freezer argument when the function already has a time_machine argument, which produced invalid syntax.

  PR [#684](https://github.com/adamchainz/time-machine/issues/684) <https://github.com/adamchainz/time-machine/pull/684>__.

• Fix the :ref:Migration CLI <migration-cli> to report positions in the rewritten file, rather than the original. Previously, positions could be off when rewrites earlier in the file changed the number of lines, or the length of the same line.

  PR [#686](https://github.com/adamchainz/time-machine/issues/686) <https://github.com/adamchainz/time-machine/pull/686>__.

... (truncated)

Commits

• 27b1d58 Version 3.5.1
• 59ead38 Add PR links to changelog
• 0e75f48 Make TimeMachineFixture always available (#675)
• 657108b Standardize the import detection test code (#694)
• 34c2a9a Adapt tests for platforms with 32-bit time_t (#693)
• 42b65d0 Only use -mno-omit-leaf-frame-pointer where supported (#692)
• 9446dcd Extend runtime fuzz tests (#691)
• 64aec53 [pre-commit.ci] pre-commit autoupdate (#676)
• effec2d Fix mocked datetime.today() rounding microseconds for far-future dates (#690)
• 656a7a0 Extend Migration CLI fuzz grammar and properties (#689)
• 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 <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