[main] Update flake.lock & generated files #3538
Conversation
e8c8943 to
68646d3
Compare
44569a6 to
65c027e
Compare
x86_64-darwin.test-6 and aarch64-darwin.test-6: |
65c027e to
59a24a2
Compare
Should be fixed by NixOS/nixpkgs#423653 (tracker)
I got a full trace locally: Relevant files in the trace (reverse order):
It looks like we're running the |
See NixOS/nixpkgs#422282 (comment). |
Yes, I fixed the |
Do you think we should apply the same snippet to both tests? Yours surely is fancier. |
IIUC, Additionally, it sounds like |
Ok sure! |
c635c46 to
7f14a99
Compare
Flake lock file updates:
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/ceb24d94c6feaa4e8737a8e2bd3cf71c3a7eaaa0?narHash=sha256-lIlUKVGCGsh0Q2EA7/6xRtKUZjaQ/ur8uUyY%2BMynHXQ%3D' (2025-07-06)
→ 'github:NixOS/nixpkgs/be9e214982e20b8310878ac2baa063a961c1bdf6?narHash=sha256-HM791ZQtXV93xtCY%2BZxG1REzhQenSQO020cu6rHtAPk%3D' (2025-07-09)
Flake lock file updates:
• Updated input 'dev-nixpkgs':
'github:NixOS/nixpkgs/ceb24d94c6feaa4e8737a8e2bd3cf71c3a7eaaa0?narHash=sha256-lIlUKVGCGsh0Q2EA7/6xRtKUZjaQ/ur8uUyY%2BMynHXQ%3D' (2025-07-06)
→ 'github:NixOS/nixpkgs/be9e214982e20b8310878ac2baa063a961c1bdf6?narHash=sha256-HM791ZQtXV93xtCY%2BZxG1REzhQenSQO020cu6rHtAPk%3D' (2025-07-09)
• Updated input 'home-manager':
'github:nix-community/home-manager/fd9e55f5fac45a26f6169310afca64d56b681935?narHash=sha256-aDDC0CHTlL7QDKWWhdbEgVPK6KwWt%2Bca0QkmHYZxMzI%3D' (2025-07-06)
→ 'github:nix-community/home-manager/bf893ad4cbf46610dd1b620c974f824e266cd1df?narHash=sha256-mCHfZhQKdTj2JhCFcqfOfa3uKZbwUkPQbd0/zPnhOE8%3D' (2025-07-13)
• Updated input 'treefmt-nix':
'github:numtide/treefmt-nix/ac8e6f32e11e9c7f153823abc3ab007f2a65d3e1?narHash=sha256-0IEdQB1nS%2BuViQw4k3VGUXntjkDp7aAlqcxdewb/hAc%3D' (2025-06-26)
→ 'github:numtide/treefmt-nix/c9d477b5d5bd7f26adddd3f96cfd6a904768d4f9?narHash=sha256-19m7P4O/Aw/6%2BCzncWMAJu89JaKeMh3aMle1CNQSIwM%3D' (2025-07-09)
7f14a99 to
c6aeeb2
Compare
Root lockfile
Dev lockfile
Generated files
This PR was most recently updated by workflow run 16252696148.
You can re-run the update by going to the workflow's page or by using the
ghcommand:If needed, you can also specify workflow inputs on the command line, using the
-F --field,-f --raw-field, or--jsonflags.See
gh workflow run --help.