GitHub
12/29/2025, 12:19 PMfaker from 38.2.0 to 39.0.0
Release notes
Sourced from faker's releases.
## Release v39.0.0
See CHANGELOG.md.
## Release v38.3.0
See CHANGELOG.md.Changelog Sourced from faker's changelog.
### v39.0.0 - 2025-12-17
• Delete duplicates in Russian professions. Thanks `@sergiusnick`.
### v38.3.0 - 2025-12-17
• Add french company RCS number. Thanks `@fabien-michel`.Commits • `b5a1bb4` Bump version: 38.3.0 → 39.0.0 • `24de141` 📝 Update CHANGELOG.md • `06ffa77` fix: Delete duplicates in Russian professions • `5d9667f` Bump version: 38.2.0 → 38.3.0 • `b9a6b1b` 📝 Update CHANGELOG.md • `9ca6bac` 💄 lint code • `63fc7f6` feat: add french company RCS number (#2264) • `4553744` Bump actions/cache from 4 to 5 (#2292) • `4244b4e` Bump actions/checkout from 5 to 6 (#2284) • See full diff in compare view Updates
time-machine from 3.1.0 to 3.2.0
Changelog
Sourced from time-machine's changelog.
## 3.2.0 (2025-12-17)
• Add attr`time_machine.naive_mode` to control how time-machine interprets naive datetimes.
The default mode is, which preserves existing behaviour: naiveMIXEDobjects anddatetimeobjects are interpreted as UTC, while naive datetime strings are interpreted as local time.date
Three alternative modes are available:
• `UTC`: naive datetimes are always interpreted as UTC.
• `LOCAL`: naive datetimes are interpreted as local time, matching Python's default semantics, and freezegun.
• `ERROR`: naive datetimes raise a, ensuring your tests are isolated from the current timezone.RuntimeError
.. note::
It’s recommended you useorLOCALto avoid confusion around naive datetimes.ERROR
`PR [#591](https://github.com/adamchainz/time-machine/issues/591) https://github.com/adamchainz/time-machine/pull/591`__. Thanks to Paolo Melchiorre for review.
Thanks to PhML, Stefaan Lippens, Matthieu Rigal, Nikita Demir, Steve Mavens, Andy Freeland, and Paul Ganssle for their input on `Issue [#257](https://github.com/adamchainz/time-machine/issues/257) https://github.com/adamchainz/time-machine/issues/257`__.
• Raisewhen attempting to start time travelling if `freezegun https://pypi.org/project/freezegun/`__ is active.RuntimeError
This change should help avoid surprises when migrating complex test suites from freezegun to time-machine.
`PR [#590](https://github.com/adamchainz/time-machine/issues/590) https://github.com/adamchainz/time-machine/pull/590`__.Commits • `1b7ac45` Version 3.2.0 • `9284e44` Change freezegun detection (#592) • `dab094e` Add
naive_mode attribute to control handling of naive datetimes (#591)
• `242f897` Raise RuntimeError if freezegun is active when starting time-machine (#590)
• `4c014f2` Upgrade dependencies (#589)
• `ef6c030` [pre-commit.ci] pre-commit autoupdate (#587)
• `96be985` Bump actions/checkout from 5 to 6 in the github-actions group (#588)
• `b57d54e` Build documentation on Python 3.14 (#586)
• See full diff in compare view
Updates importlib-metadata from 8.7.0 to 8.7.1
Changelog
Sourced from importlib-metadata's changelog.
# v8.7.1
## Bugfixes
• Fixed errors in FastPath under fork-multiprocessing. (#520)
• Removed cruft from Python 3.8. (#524)Commits • `84e9028` Finalize • `36ed6f6` Merge pull request #521 from 2xB/fix520 • `f6eee56` Rely on passthrough to designate a wrapper for its side effect. • `3c9510b` Prefer noop for degenerate behavior. • `a36bab9` Avoid if block. • `8dd2937` Decouple clear_after_fork from lru_cache and then compose. • `1da3f45` Add news fragment. • `a1c25d8` 🧎♀️ Genuflect to the types. • `4e962a8` 👹 … meltano/meltano
GitHub
12/29/2025, 2:14 PM