Bump time-machine from 3.4.0 to 3.5.0

[dependabot]

Bumps time-machine from 3.4.0 to 3.5.0.

Changelog

Sourced from time-machine's changelog.

3.5.0 (2026-08-25)

• Support None as a destination for travel() and Traveller.move_to(), meaning the current time. Use this with tick=False to freeze time at the present moment, matching freezegun’s behaviour when freeze_time() is called with no arguments.

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

• Extend the :ref:Migration CLI <migration-cli> to migrate aliased imports: import freezegun as fg and from freezegun import freeze_time as ft, plus calls using such aliases.

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

• Extend the :ref:Migration CLI <migration-cli> to migrate the pytest.mark.freeze_time marker in module-level and class-level pytestmark assignments.

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

• Extend the :ref:Migration CLI <migration-cli> to migrate freeze_time() calls and markers that pass tz_offset with a literal zero value. The argument is dropped, since a zero offset has no effect.

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

• Extend the :ref:Migration CLI <migration-cli> to migrate freeze_time() calls and markers that pass real_asyncio. The argument is dropped, whatever its value, since time-machine does not mock time.monotonic(), so asyncio event loops always see real time.

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

• Extend the :ref:Migration CLI <migration-cli> to migrate freeze_time() calls and markers with no destination argument, which freeze at the current time. None is added as the destination, using the new support for None destinations (above).

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

• Extend the :ref:Migration CLI <migration-cli> to migrate freeze_time() calls and markers that pass ignore. The argument is dropped, since it works around problems with freezegun’s module patching, which time-machine’s C-level mocking doesn’t have.

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

• Make the :ref:Migration CLI <migration-cli> report freezegun-related usages that it recognizes but cannot migrate, with their positions, like:

  .. code-block:: console

  example/tests.py:9:2: freeze_time usage not migrated

  This makes it easier to find and fix the remaining usages manually.

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

• Make the :ref:Migration CLI <migration-cli> report files that cannot be parsed, rather than skipping them silently. This helps notice files using syntax from a newer Python version than the tool is run with.

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

... (truncated)

Commits

• 19a2af0 Version 3.5.0
• def0c67 Add PR links to changelog
• c31d98c Make Migration CLI report files that cannot be parsed (#674)
• d0c4319 Extend Migration CLI to migrate FrozenDateTimeFactory (#673)
• 5593830 Improve start/stop migration performance (#672)
• 3c82f59 Extend Migration CLI to drop ignore arguments (#671)
• 5fbc5ef Extend Migration CLI to migrate raw-use start()/stop() assignments (#670)
• a1c34c6 Make Migration CLI report unmigrated freezegun usages (#669)
• a9d66bf Make Migration CLI report unmigrated freezegun usages (#668)
• c979ebc Extend Migration CLI to migrate freeze_time() calls with no destination (#667)
• 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)