build(deps): update time-machine requirement from <3.4.0 to <3.5.0

[dependabot]

Updates the requirements on time-machine to permit the latest version.

Changelog

Sourced from time-machine's changelog.

3.4.0 (2026-08-10)

• Publish wheels for Python 3.15.

  Thanks to Edgar Ramírez Mondragón in PR [#655](https://github.com/adamchainz/time-machine/issues/655) <https://github.com/adamchainz/time-machine/pull/655>__.

• Fix a reference leak in the patched datetime.datetime.utcnow() that occurred when its Python 3.12+ DeprecationWarning was raised as an error, such as under -W error. Each such call leaked a reference to the active traveller object.

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

• Extend the :ref:Migration CLI <migration-cli> to migrate patterns from freezegun’s pytest plugins, pytest-freezegun and pytest-freezer: the freezer fixture and the pytest.mark.freeze_time marker. Also make it migrate freeze_time() context managers that bind the result with as, including converting tick() method calls to shift().

  PR [#658](https://github.com/adamchainz/time-machine/issues/658) <https://github.com/adamchainz/time-machine/pull/658>. Thanks to Javier Buzzi for the initial work in PR [#562](https://github.com/adamchainz/time-machine/issues/562) <https://github.com/adamchainz/time-machine/pull/562>.

• Fix the :ref:Migration CLI <migration-cli> to handle trailing commas in freeze_time() calls when adding tick=False. Previously, it produced invalid syntax, like travel("2023-01-01",, tick=False).

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

• Fix the :ref:Migration CLI <migration-cli> to not indent imports kept from a rewritten from-import when the import doesn’t start its line, such as after if True: on one line. Previously, the kept import gained leading whitespace, producing invalid syntax.

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

3.3.1 (2026-08-04)

• Fix small rounding errors in destination calculations.

  Previously, time-machine computed destinations in floating-point seconds, which could lead to small rounding errors: up to a few hundred nanoseconds for present-day destinations, growing to several microseconds by the year 2500. This change fixes the pipeline to use integer nanoseconds throughout, so time-travel is precise for any supported date.

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

3.3.0 (2026-07-31)

• Support Python 3.15.

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

• Mock datetime.date.today() directly, for Python 3.15 support.

  Previously time-machine was mocked only indirectly, since CPython implemented it by calling cls.fromtimestamp(time.time()). Python 3.15 added a fast path that reads the system clock directly (CPython Issue [#130980](https://github.com/adamchainz/time-machine/issues/130980) <https://github.com/python/cpython/pull/130980>__), so time travel no longer affected it, which the new mock fixes. Consequently, there are new :ref:escape hatch <escape-hatch> functions: escape_hatch.datetime.date.today() and escape_hatch.datetime.datetime.today().

... (truncated)

Commits

• 2c2039c Version 3.4.0
• bb7031d Extend Migration CLI to cover freezegun's pytest plugin patterns (#658)
• 5520102 Document unmocked time sources like NumPy and SQLite (#657)
• a68d3d3 Publish wheels for Python 3.15 (#655)
• 0a225cf Fix reference leak in utcnow() when DeprecationWarning raised as error (#...
• b3ecb81 Remove sphinx-build-compatibility (#654)
• eb7ac9e Version 3.3.1
• eff8136 Use canonical timezone name in test_destination_string_naive() (#652)
• 3d59d29 Add Hypothesis fuzz tests (#653)
• c8114b0 [pre-commit.ci] pre-commit autoupdate (#650)
• 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)