Skip to content

merge queue: embarking master (3a07ae0) and #11631 together#11687

Closed
mergify[bot] wants to merge 3 commits intomasterfrom
mergify/merge-queue/3d4e0b8cc6
Closed

merge queue: embarking master (3a07ae0) and #11631 together#11687
mergify[bot] wants to merge 3 commits intomasterfrom
mergify/merge-queue/3d4e0b8cc6

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Apr 1, 2026 •
edited
Loading

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch master (3a07ae0) and #11631 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11631.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for 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

Required conditions to stay in the queue:

---
checking_base_sha: 3a07ae009bea3c219bf46574af3018bb0fe8d9b0
previous_failed_batches: []
pull_requests:
  - number: 11631
    scopes: []
scopes: []
...

jappeace-sloth and others added 3 commits March 17, 2026 23:23
@jappeace
Include provenance in Backpack unfilled requirements error
2eb46b6 
When a non-library component has unfilled Backpack signature requirements,
the error message now shows where each requirement came from (e.g.
"brought into scope by build-depends: Fail1") using the ModuleSource
information already available in the ModuleScope.

Updated the Fail3 test golden files and strengthened the test assertion
to verify provenance information is present.

Addresses #7192

run fourmalou

more formatting
@jappeace
Found the formatter!!!
fb5c87d
@mergify
Merge of #11631
c5899a4
@mergify mergify bot mentioned this pull request Apr 1, 2026
Merged
6 tasks
@mergify mergify bot closed this Apr 1, 2026
@mergify mergify bot deleted the mergify/merge-queue/3d4e0b8cc6 branch April 1, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jappeace