publish nix-cli binary cache in releases - #5
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Let fleet machines substitute the nix-cli closure from the GitHub release instead of rebuilding Nix from source on every
darwin-rebuild switch.Context
The macOS pkg workflow now also builds
.#nix-cliand exports its closure as a flat binary cache attached to the same release (<hash>.narinfo+<narhash>.nar.zst+nix-cache-info). Consumers add:narinfos are signed with the
NIX_RELEASE_SIGNING_KEYrepo secret when set (unsigned with a warning otherwise). narinfoURL:fields are rewritten fromnar/<file>.nar.zstto the flat basename because release asset names cannot contain slashes.Link to Devin session: https://app.devin.ai/sessions/45f5f87ecd904986bdbf211799db8c74
Requested by: @ethancedwards8