Today I get sha256-Yd14kla33qAx4Hy0ZdE08javvki3t+hCEc3OTO6YfkQ= instead (https://github.com/NixOS/nixpkgs/pull/301886
), and the release is written to be dated Apr 1
Did you force push the tag or should we investigate some interference between our CI system and github?
Force pushing tags is quite problematic for downstream users. If a release is broken please make a new one instead. If necessary mention that the intermediate release is broken in the release notes.
Hello, downstream NixOS maintainer here.
On march 31, our auto update automation detected that you made a tagged a new release (https://github.com/NixOS/nixpkgs/pull/300497). Our CI system downloaded the 1.7.10 tag tarball and found it to have hash sha256-Gzr0365lY9wAvmXeVungD2z44WHC+AI0a1xLWy3mCK4= (build log https://logs.ofborg.org/?attempt_id=9423b20d-3b7c-41e7-b56c-9903555ea7c6&key=nixos%2Fnixpkgs.300497 )
Today I get sha256-Yd14kla33qAx4Hy0ZdE08javvki3t+hCEc3OTO6YfkQ= instead (https://github.com/NixOS/nixpkgs/pull/301886 ), and the release is written to be dated Apr 1 Did you force push the tag or should we investigate some interference between our CI system and github?
Force pushing tags is quite problematic for downstream users. If a release is broken please make a new one instead. If necessary mention that the intermediate release is broken in the release notes.