The Bazel ZIP tooling uses fixed timestamps for build reproducibility
To guarantee reproducible ZIP archives Bazel uses a hard-coded timestamp:
static const u4 kDefaultTimestamp =
30 << 25 | 1 << 21 | 1 << 16; // January 1, 2010 in DOS time
Getting rid of these guarantees you’ll always get the exact same build output, no matter when you invoke Bazel.