Update flake/ci/flake.lock

[github-actions]

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

Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/8142186f001295e5a3239f485c8a49bf2de2695a' (2025-12-23)
  → 'github:NixOS/nixpkgs/c04833a1e584401bb63c1a63ddc51a71e6aa457a' (2026-01-01)

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 65d8346

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

Required conditions to merge

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

Reason

Pull request #231 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 36bbf7e

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

Required conditions to merge

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

Reason

Pull request #231 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 31b64f2

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

Required conditions to merge

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

Reason

Pull request #231 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]

🧪 CI Insights

Here's what we observed from your CI run for d8995bb.

🟢 All jobs passed!

But CI Insights is watching 👀

[mergify]

Merge Queue Status

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

This pull request spent 2 minutes 31 seconds in the queue, including 17 seconds running CI.
The checks were run on draft #296.

Required conditions to merge

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

Reason

Pull request #231 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.