Skip to content

merge queue: checking master (f47e959), #12068 and #12054 together#12096

Closed
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/929543d8df
Closed

merge queue: checking master (f47e959), #12068 and #12054 together#12096
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/929543d8df

Conversation

@mergify

@mergify mergify Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

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

Branch master (f47e959), #12068 and #12054 are queued together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #12054.
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:

  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 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: 453d50d4c88c4e3bcc230972107e8a910954c8ec
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12054
    scopes: []
scopes: []
...

philderbeast and others added 4 commits July 1, 2026 12:21
This change fixes the binary format mismatch between the build rules
producer and the consumer, resulting in
`Missing ByteString argument in 'ruleExecCmd'` error during builds. When
a hook creates a dynamic hook with a command for discovering dynamic
dependencies, the hook creates a result of type
([Dependency], LBS.ByteString), but the consumer decodes it as
Maybe ([Dependency], LBS.ByteString).

Added a test case to SetupHooksNonHs that covers this scenario.
Added changelog entry.

Fixes #12053
@mergify mergify Bot closed this Jul 6, 2026
@mergify mergify Bot deleted the mergify/merge-queue/929543d8df branch July 6, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants