fix(cache-warm): unblock the nightly lock refresh (gitlab API 403) and the x1 flatpak build #59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "hermes/cache-warm-gitlab403-flatpak"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two independent breaks made cache-warm fail every night since 2026-10-06/09
and froze the fleet's flake.lock at
603b74b(06.10):simple-nixos-mailserver followed a gitlab: input. GitLab now answers the
anonymous /repository/commits API — the call nix uses to resolve a branch
HEAD — with a Cloudflare challenge (403 for every project and every UA;
verified 11.10 from hermes and reproduced with a single 'nix flake update'
here). The weekly-update run died before any build, so no lock was pushed.
The API archive endpoint still serves anonymously, so the input now follows
the same nixos-26.05 HEAD as an API-archive tarball. The transitive
'blobs' input is rev-pinned and resolves via that endpoint, unchanged.
The flatpak overlay carried a diff anchored at profile/flatpak.fish:9;
flatpak 1.18.4 (nixpkgs-unstable since 29.09) reworked that function, so
'Hunk #1 FAILED' killed flatpak -> xdg-desktop-portal -> the whole
nixos-system-x1 closure. Applied via postPatch sed anchored on the line
itself instead (version-agnostic, guarded no-op if upstream ever unsets
the variable); built flatpak 1.18.4 with the overlay after the change.
PR #36 (push-before-exit) stays closed: the gating is intended, Harald
decided 24.09 on the PR; this fixes the reasons the run fails, not the gate.
Pull request closed