Skip to content

merge queue: checking master (fa68585) and #11569 together - #12214

Closed
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/b95bcbc78c
Closed

merge queue: checking master (fa68585) and #11569 together#12214
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/b95bcbc78c

Conversation

@mergify

@mergify mergify Bot commented Aug 6, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

⏳ The pull request #11569 is queued for merge and currently being checked. ⏳

Branch master (fa68585) and #11569 are queued together for merge.

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

  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-neutral = hlint
    • check-skipped = hlint
    • check-success = hlint
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
    • check-success = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-neutral = whitespace
    • check-skipped = whitespace
    • check-success = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
    • check-success = Check sdist post job
  • #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 = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Required conditions to stay in the queue:

---
checking_base_sha: fa68585d698f28b0f4bc18e810c27a8e659f5012
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 11569
    scopes: []
scopes: []
...

TeofilC and others added 2 commits August 4, 2026 16:59
@TeofilC
Add prefer-version command
7bafa2e 
The default behaviour of the solver is that we pick the latest version
of each package EXCEPT if it is a package installed in the global pkg
db, ie, package shipped with GHC.

Here we extend the existing `--prefer-oldest` flag into a
`--prefer-version=` option, which allows us to pick between
- oldest
- latest (new)
- installed-or-latest (old default)

Resolves #9669
@mergify
Merge of #11569
156c70e
@mergify mergify Bot mentioned this pull request Aug 6, 2026
Merged
6 tasks
@mergify mergify Bot closed this Aug 6, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/b95bcbc78c branch August 6, 2026 18:24
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

@TeofilC