chore: update all flake inputs (2026-07-12) #85

Closed
hermes wants to merge 2 commits from hermes:hermes/flake-update-20260712-fix into master
Collaborator

Automated flake input update (2026-07-12).

Updates:

  • argunix: 2026-06-17 → 2026-07-11 (includes disko, naersk, nixpkgs updates)
  • colmena: 2026-07-01 → 2026-07-05 (includes stable nixpkgs update)
  • hermes-agent: 2026-07-02 → 2026-07-11
  • home-manager: 2026-06-29 → 2026-07-11
  • nix-index-database: 2026-07-02 → 2026-07-07
  • nixos-hardware: 2026-06-27 → 2026-07-11
  • nixpkgs: 2026-06-30 → 2026-07-10
  • nixpkgs-master: 2026-07-02 → 2026-07-12
  • nixpkgs-unstable: 2026-07-01 → 2026-07-11
  • nixpkgs-yt-dlp: 2026-07-01 → 2026-07-11
  • nur: 2026-07-02 → 2026-07-12
  • nvf: 2026-07-02 → 2026-07-11
  • sops-nix: 2026-06-22 → 2026-07-04
  • stylix: 2026-07-01 → 2026-07-06

Several transitive inputs were restructured (removed/follows refs): argunix subsystems (disko/nixpkgs, flake-parts, naersk/fenix, treefmt-nix), hermes-agent pyproject-build-systems, nvf flake-parts/systems.

Fix Round 1

Reverted argunix, disko, naersk, flake-parts to master versions.

These inputs underwent structural changes (flake:True → flake:False or input removal) during nix flake update, breaking CI's nix-eval-jobs packages evaluation.

Still updated: nixpkgs*, hermes-agent, home-manager, nixos-hardware, nix-index-database, nvf, nur, colmena, sops-nix, stylix, stable, uv2nix, pyproject-nix.

Automated flake input update (2026-07-12). Updates: - **argunix**: 2026-06-17 → 2026-07-11 (includes disko, naersk, nixpkgs updates) - **colmena**: 2026-07-01 → 2026-07-05 (includes stable nixpkgs update) - **hermes-agent**: 2026-07-02 → 2026-07-11 - **home-manager**: 2026-06-29 → 2026-07-11 - **nix-index-database**: 2026-07-02 → 2026-07-07 - **nixos-hardware**: 2026-06-27 → 2026-07-11 - **nixpkgs**: 2026-06-30 → 2026-07-10 - **nixpkgs-master**: 2026-07-02 → 2026-07-12 - **nixpkgs-unstable**: 2026-07-01 → 2026-07-11 - **nixpkgs-yt-dlp**: 2026-07-01 → 2026-07-11 - **nur**: 2026-07-02 → 2026-07-12 - **nvf**: 2026-07-02 → 2026-07-11 - **sops-nix**: 2026-06-22 → 2026-07-04 - **stylix**: 2026-07-01 → 2026-07-06 Several transitive inputs were restructured (removed/follows refs): argunix subsystems (disko/nixpkgs, flake-parts, naersk/fenix, treefmt-nix), hermes-agent pyproject-build-systems, nvf flake-parts/systems. ## Fix Round 1 Reverted `argunix`, `disko`, `naersk`, `flake-parts` to master versions. These inputs underwent structural changes (`flake:True → flake:False` or input removal) during `nix flake update`, breaking CI's `nix-eval-jobs` packages evaluation. **Still updated:** nixpkgs\*, hermes-agent, home-manager, nixos-hardware, nix-index-database, nvf, nur, colmena, sops-nix, stylix, stable, uv2nix, pyproject-nix.
chore: update all flake inputs (2026-07-12)
Some checks failed
argunix: evaluation evaluation failed: nix-eval-jobs (packages.x86_64-linux) exited with status Some(1)
e566539072
Author
Collaborator

👀 CI has not started yet

After ~15 minutes of polling the Forgejo commit statuses API for commit 44b56ae0, no CI checks have been posted.

Possible causes:

  • Fork-based PR: This PR is from the hermes/nixos-configs fork, which argunix (CI) may not automatically evaluate
  • CI backlog: argunix may poll on a longer schedule or have a queue backlog
  • No CI trigger: The webhook may not be configured for fork PRs

Action taken: CI monitoring completed — no failures to fix since no checks ran. This PR will re-evaluate automatically on the next push (e.g. a rebase or a comment triggering CI). If CI remains stuck, a human may need to trigger it manually or check argunix's configuration for fork PR support.

👀 **CI has not started yet** After ~15 minutes of polling the Forgejo commit statuses API for commit `44b56ae0`, no CI checks have been posted. **Possible causes:** - **Fork-based PR:** This PR is from the `hermes/nixos-configs` fork, which argunix (CI) may not automatically evaluate - **CI backlog:** argunix may poll on a longer schedule or have a queue backlog - **No CI trigger:** The webhook may not be configured for fork PRs **Action taken:** CI monitoring completed — no failures to fix since no checks ran. This PR will re-evaluate automatically on the next push (e.g. a rebase or a comment triggering CI). If CI remains stuck, a human may need to trigger it manually or check argunix's configuration for fork PR support.
hermes closed this pull request 2026-07-12 07:49:22 +02:00

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pim/nixos-configs!85
No description provided.