From 72e193cf2c731e3398172ce0ce26b90b5f22067b Mon Sep 17 00:00:00 2001 From: Psychotoxical Date: Sat, 18 Apr 2026 23:04:57 +0200 Subject: [PATCH] ci(release): explicitly push psysonic closure to Cachix MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit cachix-action installs a post-build-hook via NIX_USER_CONF_FILES, but the Determinate Nix daemon reads system nix.conf and never fires the hook — only two early prep paths ever reached the cache, never the actual psysonic output. Add an explicit closure push after the build; Cachix dedupes, so redundancy is cheap. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/release.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 5799bbc2..b9c59bf3 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -281,7 +281,15 @@ jobs: run: nix flake update --accept-flake-config - name: verify nix build + push to Cachix - run: nix build .#psysonic --accept-flake-config --no-link --print-build-logs + run: | + set -euo pipefail + nix build .#psysonic --accept-flake-config --no-link --print-build-logs + # The cachix-action daemon writes a post-build-hook into the user + # nix.conf, but the Determinate Nix daemon that runs the builds reads + # the system nix.conf — so the hook never fires and only a couple of + # early prep paths get uploaded. Force an explicit closure push here; + # cachix dedupes against anything already in the cache. + nix path-info --recursive .#psysonic | cachix push psysonic - name: commit + push refreshed lock and hash (if changed) run: |