Repository navigation
Conversation
Bare `nix run nixpkgs#...` pulls the latest nixpkgs from the registry. That can differ from run to run, and it costs an extra download. Add `--inputs-from .` so these calls use the nixpkgs pinned in flake.lock, as the qemu build step already does. Assisted-by: Claude <noreply@anthropic.com>
tkren
approved these changes
Nov 12, 2026
Package version diff: none (aarch64-linux, x86_64-linux) |
mmlb
enabled auto-merge
November 12, 2026 19:53
mmlb
added this pull request to the merge queue
Nov 12, 2026
Any commits made after this event will not be merged.
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.
What kind of change does this PR introduce?
Gardening
What is the current behavior?
A bunch of workflows use
nix run nixpkgs#...which does not guarantee what revision of nixpkgs is used to fetch those tools. This nixpkgs is very likely not the nixpkgs we use in the flake so gets fetched from upstream binary cache.What is the new behavior?
Tools are pulled in from the nixpkgs revision we use in the repo. So every run uses the same version until nixpkgs is changed. We also use the same version of tools outside of nix builds as in. We now also get nixpkgs from our s3 binary cache and share it with any later nix invocations. Overall better usage of nix.