Cache revalidation fails if files have Unix epoch timestamp (Jan 1 1970)

[cpboyd]

Summary

I'm building a Next.js 13 project and this is the second time I've experienced this (since enough time passed that I forgot the original issue).

Figured I'd log this as a discussion to help anyone else who might unknowingly experience this issue.

Basically, kaniko has a --reproducible option that clears the timestamps from all files so that every Docker build will be reproducible and consistent.

Is there any specific rationale that the cache fails if files have a timestamp of 1970? (i.e. was this an intentional design decision to provide a way to break updates on specific pages?)

Additional information

`next info`:

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041
Binaries:
  Node: 22.14.0
  npm: 11.2.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.9
  eslint-config-next: 13.0.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5
Next.js Config:
  output: standalone

### Example

_No response_