Skip to content

Add Dependabot checking for uv updates#11720

Merged
mergify[bot] merged 1 commit intohaskell:masterfrom
geekosaur:dependabot-uv
Apr 11, 2026
Merged

Add Dependabot checking for uv updates#11720
mergify[bot] merged 1 commit intohaskell:masterfrom
geekosaur:dependabot-uv

Conversation

@geekosaur
Copy link
Copy Markdown
Collaborator

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions). only relevant on master

@geekosaur geekosaur added continuous-integration dependencies Pull requests that update a dependency file labels Apr 9, 2026
@geekosaur
Copy link
Copy Markdown
Collaborator Author

geekosaur commented Apr 9, 2026

Okay, something's weird with Mergify. It's saying this PR is ready to be queued, but (a) not all required checks have completed (b) it doesn't have any reviews (c) it's still a draft (d) no merge labels.

There's another PR (#11684) that has no merge labels and is otherwise not ready, but every few days Mergify tries to put it in the merge queue and then rejects it due to it not being ready (in particular, no reviews yet IIRC). I checked its status and it seems to recognize that it doesn't in fact match any of the rules to queue it. So I don't think this is a problem on our side, and I really hope Mergify doesn't start auto-queueing this one too.

@geekosaur geekosaur marked this pull request as ready for review April 9, 2026 02:04
@geekosaur geekosaur added merge me Tell Mergify Bot to merge and removed attention: needs-review labels Apr 9, 2026
@mergify mergify bot added ready and waiting Mergify is waiting out the cooldown period merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels Apr 9, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 11, 2026

Merge Queue Status

This pull request spent 1 hour 38 minutes 51 seconds in the queue, including 1 hour 28 minutes 28 seconds running CI.

Waiting for:

  • check-neutral = Validate post job

or

  • check-skipped = Validate post job

or

  • check-success = Validate post job
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, 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 queue comment.

mergify bot added a commit that referenced this pull request Apr 11, 2026
@mergify mergify bot added dequeued and removed queued labels Apr 11, 2026
@geekosaur
Copy link
Copy Markdown
Collaborator Author

@Mergifyio queue

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 11, 2026

Merge Queue Status

This pull request spent 1 hour 52 minutes 59 seconds in the queue, including 1 hour 41 minutes 38 seconds running CI.

Required conditions to merge
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

@mergify mergify bot added queued and removed dequeued labels Apr 11, 2026
mergify bot added a commit that referenced this pull request Apr 11, 2026
@mergify mergify bot merged commit 3c4c113 into haskell:master Apr 11, 2026
408 of 409 checks passed
@mergify mergify bot removed the queued label Apr 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

continuous-integration dependencies Pull requests that update a dependency file merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants