mirror of
https://github.com/3proxy/3proxy.git
synced 2026-08-26 09:55:48 +08:00
754ba7115a
The build date stored in version.h is now the single time source for a release. Each package workflow converts it to SOURCE_DATE_EPOCH and passes that into the build containers, the debian changelog entry is stamped from it rather than from the build clock, and rpmbuild is told to use it as the build time and to clamp file mtimes to it. rpm also records the build host, which is a container id and therefore differs on every run, so pin it as well - otherwise the timestamps alone do not make the package reproducible. Rebuilding the same commit now produces byte identical packages, verified for both formats by building twice and comparing checksums. In the version workflow the clock is read exactly once, when a new build date is minted. YEAR3PROXY is derived from the build date instead of being read separately, so the two cannot straddle a year boundary and a re-run in a later year no longer rewrites version.h. |
||
|---|---|---|
| .. | ||
| build-rpm-arm64.yml | ||
| build-rpm-armhf.yml | ||
| build-rpm-x86-64.yml | ||
| build-watcom.yml | ||
| build-win32.yml | ||
| build-win64.yml | ||
| build-win-msys2-ucrt64.yml | ||
| build-winarm64.yml | ||
| c-cpp-cmake.yml | ||
| c-cpp-Linux.yml | ||
| c-cpp-MacOS.yml | ||
| c-cpp-Windows.yml | ||
| docker-test.yml | ||
| docker.yml | ||
| update-version.yml | ||