Skip to content

Backport #11171: Fix docs, PackageInfo_* modules and cabal-version: 3.12 #11323

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
mergify merged 1 commit into from
Dec 5, 2025
Merged

Backport #11171: Fix docs, PackageInfo_* modules and cabal-version: 3.12 #11323

mergify merged 1 commit into from
Dec 5, 2025
+8 −0

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Dec 4, 2025

See:

Template B: This PR does not modify behaviour or interface

  • Patches conform to the coding conventions. Yes.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions). Not applicable.
This is an automatic backport of pull request #11171 done by [Mergify](https://mergify.com).

@mergify mergify bot mentioned this pull request Dec 4, 2025
Merged
2 tasks
@mergify mergify bot added the backport label Dec 4, 2025
@Mikolaj Mikolaj added the merge me Tell Mergify Bot to merge label Dec 4, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Dec 4, 2025 •
edited
Loading

Merge Queue Status

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

This pull request spent 1 hour 39 minutes 20 seconds in the queue, including 1 hour 29 minutes 5 seconds running CI.
The checks were run on draft #11326.

Required conditions to merge
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #approved-reviews-by >= 1 [🛡 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 = 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

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 requeue comment.

@mergify mergify bot added the queued label Dec 4, 2025
mergify bot added a commit that referenced this pull request Dec 4, 2025
@mergify
Merge of #11323
2d66315
@mergify mergify bot mentioned this pull request Dec 4, 2025
Closed
54 tasks
@mergify mergify bot added dequeued and removed queued labels Dec 5, 2025
@Mikolaj
Copy link
Member

Mikolaj commented Dec 5, 2025

@mergify rebase

@mergify
Copy link
Contributor Author

mergify bot commented Dec 5, 2025

rebase

✅ Branch has been successfully rebased

@Mikolaj Mikolaj force-pushed the mergify/bp/3.16/pr-11171 branch from 6507333 to 482ae4a Compare December 5, 2025 09:51
@mergify mergify bot removed the dequeued label Dec 5, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Dec 5, 2025 •
edited
Loading

Merge Queue Status

✅ The pull request has been merged

This pull request spent 11 minutes 22 seconds in the queue, with no time running CI.
The checks were run in-place.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 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 = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • 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 = 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

@mergify mergify bot added the queued label Dec 5, 2025
@mergify mergify bot merged commit 69ed86e into 3.16 Dec 5, 2025
59 checks passed
@mergify mergify bot deleted the mergify/bp/3.16/pr-11171 branch December 5, 2025 11:50
@mergify mergify bot removed the queued label Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Mikolaj Mikolaj Mikolaj approved these changes

@geekosaur geekosaur geekosaur approved these changes

Assignees

No one assigned

Labels

backport merge me Tell Mergify Bot to merge

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@Mikolaj @geekosaur @mpilgrem