Update flake/nixos/flake.lock

[github-actions]

Automated changes by the update-flake-lock GitHub Action.

Flake lock file updates:

• Updated input 'angrr':
    'github:linyinfeng/angrr/388f58e5a949b21e56fb543aa9e11b2cf79c7f50' (2025-12-23)
  → 'github:linyinfeng/angrr/1c129486063f7dd932b5ea5a43fb194d4abacfed' (2026-01-14)
• Updated input 'angrr/nix-darwin':
    'github:nix-darwin/nix-darwin/5fb45ece6129bd7ad8f7310df0ae9c00bae7c562' (2025-12-18)
  → 'github:nix-darwin/nix-darwin/7b1d394e7d9112d4060e12ef3271b38a7c43e83b' (2026-01-12)
• Updated input 'angrr/treefmt-nix':
    'github:numtide/treefmt-nix/42d96e75aa56a3f70cab7e7dc4a32868db28e8fd' (2025-12-17)
  → 'github:numtide/treefmt-nix/e96d59dff5c0d7fddb9d113ba108f03c3ef99eca' (2026-01-11)
• Updated input 'flake-parts':
    'github:hercules-ci/flake-parts/a34fae9c08a15ad73f295041fec82323541400a9' (2025-12-15)
  → 'github:hercules-ci/flake-parts/80daad04eddbbf5a4d883996a73f3f542fa437ac' (2026-01-11)
• Updated input 'impermanence':
    'github:nix-community/impermanence/4b3e914cdf97a5b536a889e939fb2fd2b043a170' (2025-01-25)
  → 'github:nix-community/impermanence/82e5bc4508cab9e8d5a136626276eb5bbce5e9c5' (2026-01-07)
• Added input 'impermanence/home-manager':
    'github:nix-community/home-manager/7419250703fd5eb50e99bdfb07a86671939103ea' (2025-05-23)
• Added input 'impermanence/home-manager/nixpkgs':
    follows 'impermanence/nixpkgs'
• Added input 'impermanence/nixpkgs':
    'github:nixos/nixpkgs/063f43f2dbdef86376cc29ad646c45c46e93234c' (2025-05-23)
• Updated input 'jovian':
    'github:Jovian-Experiments/Jovian-NixOS/9d0abe57d633a6e08d72865a761891a8c81e740f' (2025-12-24)
  → 'github:Jovian-Experiments/Jovian-NixOS/544a1396c5a75fe832ae7a2a097bb760701ccd50' (2026-01-14)
• Updated input 'nixos-hardware':
    'github:nixos/nixos-hardware/c5db9569ac9cc70929c268ac461f4003e3e5ca80' (2025-12-24)
  → 'github:nixos/nixos-hardware/7297dfc69ae9b06e984a6f69900ce25e67c76f46' (2026-01-15)
• Updated input 'nixos-wsl':
    'github:nix-community/NixOS-WSL/be4af8042e7a61fa12fda58fe9a3b3babdefe17b' (2025-12-15)
  → 'github:nix-community/NixOS-WSL/d0d3636b9d174c4558e3bbb18e194d970505fed8' (2026-01-14)
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/a6531044f6d0bef691ea18d4d4ce44d0daa6e816' (2025-12-21)
  → 'github:NixOS/nixpkgs/1412caf7bf9e660f2f962917c14b1ea1c3bc695e' (2026-01-13)
• Updated input 'rust-overlay':
    'github:oxalica/rust-overlay/5359a4fdc3fa9baa2edcf49758d404dfeeca7743' (2025-12-24)
  → 'github:oxalica/rust-overlay/1cd63408e71cc0e6a89ff2cb7c4107214e2523cc' (2026-01-15)
• Updated input 'ucodenix':
    'github:e-tho/ucodenix/98f3557566919631c392b87a9734a5aa6319552c' (2025-12-09)
  → 'github:e-tho/ucodenix/8ea2a75e3e46c4268fc55dba197bfd95fd6c2896' (2025-12-29)
• Updated input 'ucodenix/cpu-microcodes':
    'github:platomav/CPUMicrocodes/4b18748b5cfc10464e4c5c5d93ead73a29482fb0' (2025-12-06)
  → 'github:platomav/CPUMicrocodes/8bdf34aec2052ab12ae017eb21fe395f6329f6c4' (2025-12-22)

Running GitHub Actions on this PR

GitHub Actions will not run workflows on pull requests which are opened by a GitHub Action.

To run GitHub Actions workflows on this PR, close and re-open this pull request.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 241d1a6

This pull request spent 1 minute in the queue, including 23 seconds running CI.
The checks were run on draft #237.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/nixos/flake.lock #230
• #check-failure==0
• #commits-behind <= 10
  • Update flake/nixos/flake.lock #230
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/nixos/flake.lock #230

Reason

Pull request #230 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 42a221c

This pull request spent 8 seconds in the queue, including 1 second running CI.
The checks were run on draft #242.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/nixos/flake.lock #230
• #check-failure==0
• #commits-behind <= 10
  • Update flake/nixos/flake.lock #230
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/nixos/flake.lock #230

Reason

Pull request #230 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 15abed2

This pull request spent 2 minutes 37 seconds in the queue, including 18 seconds running CI.
The checks were run on draft #456.

Required conditions to merge

• #approved-reviews-by>=1
  • Update flake/nixos/flake.lock #230
• #check-failure==0
• #commits-behind <= 10
  • Update flake/nixos/flake.lock #230
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Update flake/nixos/flake.lock #230

Reason

Pull request #230 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.