lifehackerhansol 5fa351a3a0 treewide: use deterministic-zip ... https://github.com/timo-reymann/deterministic-zip This solves a logistics issue; zip files always include the modified timestamp of a file. This doesn't sound bad until you realize that GitHub Actions always re-clones the entire repository, and the timestamp is guaranteed to be different. Because of this, every time we run our Actions workflow, the zip will have a different checksum, causing git to re-commit *every single file* to the frontend repository, causing long workflow times due to the sheer size of each commit. deterministic-zip hopefully solves this issue by forcing the modified timestamp to one hardcoded in its binary, so here is to hoping we don't abuse our git repo any further.		2024-01-14 21:59:35 -08:00
..
EDGE_OS_1.36	EDGE (v1.4, v1.37, v1.41, v1.36)	2023-08-15 06:05:36 -07:00
EDGE_OS_1.37	EDGE (v1.4, v1.37, v1.41, v1.36)	2023-08-15 06:05:36 -07:00
EDGE_OS_1.40	EDGE (v1.4, v1.37, v1.41, v1.36)	2023-08-15 06:05:36 -07:00
EDGE_OS_1.41	EDGE (v1.4, v1.37, v1.41, v1.36)	2023-08-15 06:05:36 -07:00
Makefile	treewide: use deterministic-zip	2024-01-14 21:59:35 -08:00