Update flake.lock

[github-actions]

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

Flake lock file updates:

• Updated input 'erosanix':
    'github:emmanuelrosa/erosanix/40446938af0e4323fc8fa720f4590d993c0a1217' (2025-12-19)
  → 'github:emmanuelrosa/erosanix/63d0808c548dbfab937b5511c47eeff1dc0193b8' (2025-12-31)
• Updated input 'nixpkgs':
    'github:nixos/nixpkgs/a6531044f6d0bef691ea18d4d4ce44d0daa6e816' (2025-12-21)
  → 'github:nixos/nixpkgs/cad22e7d996aea55ecab064e84834289143e44a0' (2025-12-30)

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 ef76fa5

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

Required conditions to merge

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

Reason

Pull request #228 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 4879e41

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

Required conditions to merge

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

Reason

Pull request #228 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 5c470fd

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

Required conditions to merge

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

Reason

Pull request #228 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 6e95452

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

Required conditions to merge

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

Reason

Pull request #228 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 5d9ae20.

🟢 All jobs passed!

But CI Insights is watching 👀

[mergify]

Merge Queue Status

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

This pull request spent 39 seconds in the queue, including 15 seconds running CI.
The checks were run on draft #285.

Required conditions to merge

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

Reason

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