Only flake.lock is modified (no Nix expressions, no config, no secrets). The changes are all rev/narHash/lastModified bumps across multiple inputs:
Input
Change
buildbot-nix
Updated to rev 891f2bab (2026-04-17)
colmena
Updated to rev 56c666e1
flake-parts (all instances)
Updated to rev f7c1a2d3 (2026-05-09)
home-manager
Updated to rev fab3fd73 (2026-04-18)
nixpkgs (nixunstable)
Updated to rev 87611ef4
nixpkgs-stable
Updated to rev 8792fab9 (2026-04-18)
nuenv
Updated to rev f5901329
treefmt-nix
Updated to rev 0d14a58a
nix-index-database
Updated to rev d233902
nix-darwin
Updated to rev a7ecea3
sops-nix
Updated to rev 1367315
vscode-server
Updated to rev ad57d8f
nixvim
Updated to rev b7bde177
devenv
Updated to rev 5482f113
Structural cleanup:hercules-ci-effects and its associated flake-parts instance were removed from the buildbot-nix input graph — this is consistent with upstream buildbot-nix dropping that dependency.
Assessment
All changes are version bumps with new narHash values (Nix will verify content integrity at build time)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Automated weekly flake.lock update.
Generated by Gitea Actions.
Flake Lock Update Review
✅ LGTM — automated
flake.lockbump, looks clean.What changed
Only
flake.lockis modified (no Nix expressions, no config, no secrets). The changes are allrev/narHash/lastModifiedbumps across multiple inputs:buildbot-nix891f2bab(2026-04-17)colmena56c666e1flake-parts(all instances)f7c1a2d3(2026-05-09)home-managerfab3fd73(2026-04-18)nixpkgs(nixunstable)87611ef4nixpkgs-stable8792fab9(2026-04-18)nuenvf5901329treefmt-nix0d14a58anix-index-databased233902nix-darwina7ecea3sops-nix1367315vscode-serverad57d8fnixvimb7bde177devenv5482f113Structural cleanup:
hercules-ci-effectsand its associatedflake-partsinstance were removed from thebuildbot-nixinput graph — this is consistent with upstreambuildbot-nixdropping that dependency.Assessment
narHashvalues (Nix will verify content integrity at build time)No concerns. Safe to merge whenever ready.