This is a routine automated flake.lock update generated by Gitea Actions. Reviewed as read-only (not a repo owner, no merge).
Summary
Only flake.lock is modified — no Nix expressions, modules, or configuration changed. All modifications are expected hash/revision/timestamp bumps for the following inputs:
Input
Notes
buildbot-nix
Updated; also drops flake-parts and hercules-ci-effects from its direct inputs (upstream input cleanup)
darwin (nix-darwin)
Bumped
flake-parts / flake-parts_2 / flake-parts_3
Bumped to same new rev; input graph reorganized (flake-parts node deduplicated, nixpkgs-lib pointer updated)
minecraft (nix-minecraft)
Bumped
niks3
Bumped
nix-hardware
Bumped
nixpkgs-lib
Bumped
nixpkgs_3 / nixpkgs_4 / nixpkgs_5 / nixunstable
All bumped to newer commits
nixvimunstable
Bumped
nurpkgs (NUR)
Bumped
vscode-extensions
Bumped
nixos-wsl
Bumped
Input Graph Changes
Beyond simple version bumps, there is minor input-graph restructuring:
buildbot drops flake-parts and hercules-ci-effects from its declared inputs (upstream decided to manage those differently).
flake-parts nodes are renumbered/repointed as a result — flake-parts now points to the hercules-ci-owned one (previously flake-parts_2), and the graph collapses a redundant node.
nixvimunstable and nurpkgs now reference the renumbered flake-parts nodes accordingly.
Root flake now references flake-parts instead of flake-parts_2 (same effective input after renumbering).
These graph changes are consistent with upstream dependency cleanup and are expected in automated lock updates.
Verdict
✅LGTM — purely mechanical lock file update, all changes are version bumps + expected input graph renumbering. No security concerns. Safe to merge.
## Flake Lock Update Review
This is a routine automated flake.lock update generated by Gitea Actions. Reviewed as read-only (not a repo owner, no merge).
### Summary
Only `flake.lock` is modified — no Nix expressions, modules, or configuration changed. All modifications are expected hash/revision/timestamp bumps for the following inputs:
| Input | Notes |
|-------|-------|
| `buildbot-nix` | Updated; also drops `flake-parts` and `hercules-ci-effects` from its direct inputs (upstream input cleanup) |
| `darwin` (nix-darwin) | Bumped |
| `flake-parts` / `flake-parts_2` / `flake-parts_3` | Bumped to same new rev; input graph reorganized (flake-parts node deduplicated, `nixpkgs-lib` pointer updated) |
| `minecraft` (nix-minecraft) | Bumped |
| `niks3` | Bumped |
| `nix-hardware` | Bumped |
| `nixpkgs-lib` | Bumped |
| `nixpkgs_3` / `nixpkgs_4` / `nixpkgs_5` / `nixunstable` | All bumped to newer commits |
| `nixvimunstable` | Bumped |
| `nurpkgs` (NUR) | Bumped |
| `vscode-extensions` | Bumped |
| `nixos-wsl` | Bumped |
### Input Graph Changes
Beyond simple version bumps, there is minor input-graph restructuring:
- `buildbot` drops `flake-parts` and `hercules-ci-effects` from its declared inputs (upstream decided to manage those differently).
- `flake-parts` nodes are renumbered/repointed as a result — `flake-parts` now points to the hercules-ci-owned one (previously `flake-parts_2`), and the graph collapses a redundant node.
- `nixvimunstable` and `nurpkgs` now reference the renumbered flake-parts nodes accordingly.
- Root flake now references `flake-parts` instead of `flake-parts_2` (same effective input after renumbering).
These graph changes are consistent with upstream dependency cleanup and are expected in automated lock updates.
### Verdict
✅ **LGTM** — purely mechanical lock file update, all changes are version bumps + expected input graph renumbering. No security concerns. Safe to merge.
Acknowledged. The automated update conflicted with changes already in the branch. A fresh nix flake update on a clean base will be needed — either via a new automated run or manually when ready.
Acknowledged. The automated update conflicted with changes already in the branch. A fresh `nix flake update` on a clean base will be needed — either via a new automated run or manually when ready.
Pull request closed
Please reopen this pull request to perform a merge.
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.
klaatu
Automated weekly flake.lock update.
Generated by Gitea Actions.
Flake Lock Update Review
This is a routine automated flake.lock update generated by Gitea Actions. Reviewed as read-only (not a repo owner, no merge).
Summary
Only
flake.lockis modified — no Nix expressions, modules, or configuration changed. All modifications are expected hash/revision/timestamp bumps for the following inputs:buildbot-nixflake-partsandhercules-ci-effectsfrom its direct inputs (upstream input cleanup)darwin(nix-darwin)flake-parts/flake-parts_2/flake-parts_3nixpkgs-libpointer updated)minecraft(nix-minecraft)niks3nix-hardwarenixpkgs-libnixpkgs_3/nixpkgs_4/nixpkgs_5/nixunstablenixvimunstablenurpkgs(NUR)vscode-extensionsnixos-wslInput Graph Changes
Beyond simple version bumps, there is minor input-graph restructuring:
buildbotdropsflake-partsandhercules-ci-effectsfrom its declared inputs (upstream decided to manage those differently).flake-partsnodes are renumbered/repointed as a result —flake-partsnow points to the hercules-ci-owned one (previouslyflake-parts_2), and the graph collapses a redundant node.nixvimunstableandnurpkgsnow reference the renumbered flake-parts nodes accordingly.flake-partsinstead offlake-parts_2(same effective input after renumbering).These graph changes are consistent with upstream dependency cleanup and are expected in automated lock updates.
Verdict
✅ LGTM — purely mechanical lock file update, all changes are version bumps + expected input graph renumbering. No security concerns. Safe to merge.
Closing, as the underlying branch has changes and conflicts with the
flake.lock.Acknowledged. The automated update conflicted with changes already in the branch. A fresh
nix flake updateon a clean base will be needed — either via a new automated run or manually when ready.Pull request closed