Skip to content

Comments

Update flake/ci/flake.lock#231

Closed
github-actions[bot] wants to merge 2 commits intomasterfrom
update_flake_ci_flake
Closed

Update flake/ci/flake.lock#231
github-actions[bot] wants to merge 2 commits intomasterfrom
update_flake_ci_flake

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 26, 2025

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/13868c071cc73a5e9f610c47d7bb08e5da64fdd5' (2026-01-14)

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 mergify bot requested a review from DaRacci December 26, 2025 00:20
@mergify mergify bot added the queued label Dec 26, 2025
mergify bot added a commit that referenced this pull request Dec 26, 2025
mergify bot added a commit that referenced this pull request Dec 26, 2025
mergify bot added a commit that referenced this pull request Dec 26, 2025
@mergify
Copy link
Contributor

mergify bot commented Dec 26, 2025

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

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 mergify bot added the merge-queued label Dec 26, 2025
mergify bot added a commit that referenced this pull request Dec 26, 2025
@github-actions github-actions bot force-pushed the update_flake_ci_flake branch from 65d8346 to 36bbf7e Compare December 27, 2025 00:19
@mergify mergify bot added queued and removed dequeued labels Dec 27, 2025
mergify bot added a commit that referenced this pull request Dec 27, 2025
@mergify
Copy link
Contributor

mergify bot commented Dec 27, 2025

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

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 mergify bot added dequeued and removed queued labels Dec 27, 2025
@github-actions github-actions bot force-pushed the update_flake_ci_flake branch from 36bbf7e to 497de6d Compare December 28, 2025 00:22
@mergify mergify bot added queued and removed dequeued labels Dec 28, 2025
mergify bot added a commit that referenced this pull request Dec 28, 2025
@mergify mergify bot added queued and removed dequeued labels Jan 16, 2026
mergify bot added a commit that referenced this pull request Jan 16, 2026
mergify bot added a commit that referenced this pull request Jan 16, 2026
mergify bot added a commit that referenced this pull request Jan 16, 2026
@mergify mergify bot added the merge-queued label Jan 16, 2026
@mergify
Copy link
Contributor

mergify bot commented Jan 16, 2026

Merge Queue Status

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

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

Required conditions to merge

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant