chore(auto): update flake inputs - #1787
Merged
Merged
Conversation
void-commander-brain-freeze
Bot
force-pushed
the
automatic-updates
branch
2 times, most recently
from
September 26, 2026 00:11
8ff2e49 to
a81c8fd
Compare
void-commander-brain-freeze
Bot
force-pushed
the
automatic-updates
branch
from
September 27, 2026 00:26
a81c8fd to
26e72ef
Compare
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.
CI repair report
What I changed
Nothing.
nix run .#world -- check(nix flake check --impure) passes cleanly onthis branch: 58/58 outputs green, zero failures, and the warning set is identical
between the provided
.ci-check.logand a fresh run I did myself. I could not findanything in this repo's own
.nixfiles that the input bump broke or that adeprecation warning points back to — see below for what I checked and why each
warning is not something this repo can fix.
Warnings investigated, and why none needed a change here
evaluation warning: stdenv.isLinux is deprecated, use stdenv.hostPlatform.isLinux insteadand the matching
stdenv.isDarwinwarning. I grepped the whole tree (excluding/nix/store) forisLinux/isDarwinand this repo doesn't reference eitherattribute anywhere —
flake/packages.nixalready usespkgs.stdenv.hostPlatform.isLinux. The warning fires from inside a transitivedependency (nixpkgs itself and/or one of the pinned flake inputs) that still
reads the old attribute internally. There's no line in this repo to change; fixing
it means patching nixpkgs or a third-party flake input, not this config.
evaluation warning: The package 'devenv-test'/'devenv-up' is deprecated. Use the corresponding devenv <cmd> commands.These packages are auto-generated bydevenv.flakeModulefor every shell underdevenv.shells(wired up inflake/devenv.nix) as a backward-compatiblenix buildtarget; the deprecationnotice is devenv's own, not something this repo's shell definitions can silence
without removing the packages. Both
flake/buildkite-pipeline.nixandflake/github-actions.nixalready excludedevenv-upfrom their CI buildmatrices, so nothing here actually builds it — it's inert noise.
evaluation warning: You have not yet specified rekey.hostPubkey for your host test./...host nixos.These belong to thetestandinstaller(nixos)nixosConfigurations, and the warning text says outright this is intentional
("so you can initially deploy your system to read the actual pubkey"). This is
agenix-rekey secrets/key material behavior, unrelated to the input bump — per
the constraints for this task I left it alone rather than touch anything in
that area.
warning: Using 'builtins.derivation' to create a derivation named 'options.json' ...— not referenced anywhere in this repo's.nixfileseither; it comes from options-doc generation inside one of the flake inputs
(agenix-rekey or similar).
I compared the warning/pass-fail lines from the supplied
.ci-check.logagainst afresh
nix run .#world -- checkrun on this branch and they matched exactly, sonone of this is new fallout from the update that isn't already visible in the log.
Needs a human
Nothing new from this update. The four warnings above are pre-existing/upstream
noise, not regressions caused by this bump, and none of them have an actionable
fix inside this repository without either patching a third-party flake input
(devenv, nixpkgs) or touching secrets/key-material configuration, both of which
are out of scope for an automated pass.
🤖 Generated with Claude Code