Skip to content

3.19 cabal version bumps on master branch for the 3.18 release#12128

Merged
mergify[bot] merged 6 commits into
haskell:masterfrom
Mikolaj:3.19-cabal-version-bumps
Jul 24, 2026
Merged

3.19 cabal version bumps on master branch for the 3.18 release#12128
mergify[bot] merged 6 commits into
haskell:masterfrom
Mikolaj:3.19-cabal-version-bumps

Conversation

@Mikolaj

@Mikolaj Mikolaj commented Jul 20, 2026

Copy link
Copy Markdown
Member

Template B: This PR does not modify behaviour or interface

This is the counterpart of #12104 for the master branch. Most commits are cherry-picked without changes, which tells me I should have put them in a PR on master and backported to 3.18 instead. Oh well. However, in this one we didn't need to hack around CI failures due to a proper fix, so the workaround commit is not cherry-picked.

Edit: I've also bumped hooks-exe to 3.19 so maybe we won't need to forward port the hooks-exe version fix from 3.18 to master.

@Mikolaj
Mikolaj force-pushed the 3.19-cabal-version-bumps branch from 4b7011e to 0b87dff Compare July 20, 2026 08:54
@Mikolaj
Mikolaj requested a review from ffaf1 July 20, 2026 10:15
@Mikolaj

Mikolaj commented Jul 20, 2026

Copy link
Copy Markdown
Member Author

@ffaf1: please kindly verify what I did with hooks-exe agrees with what you are planning for 3.18 and suggest corrections otherwise.

@Mikolaj Mikolaj added squash+merge me Tell Mergify Bot to squash-merge merge me Tell Mergify Bot to merge and removed squash+merge me Tell Mergify Bot to squash-merge labels Jul 20, 2026

@ffaf1 ffaf1 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, many thanks!

@ffaf1

ffaf1 commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

I think this does not require Template A.

@mergify mergify Bot added the ready and waiting Mergify is waiting out the cooldown period label Jul 22, 2026
@mergify mergify Bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels Jul 24, 2026
@mergify

mergify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 hours 9 minutes 15 seconds in the queue, including 1 hour 58 minutes 26 seconds running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • 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
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection] (documentation)
  • 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

  • Doctest Cabal
  • Meta checks
  • docs/readthedocs.org:cabal
  • Validate post job
  • fourmolu
  • hlint
  • Bootstrap post job
  • whitespace
  • Check sdist post job
  • Changelogs

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.

@zlonast

zlonast commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

@Mergifyio queue

@mergify

mergify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 hours 10 minutes 5 seconds in the queue, including 1 hour 59 minutes running CI.

Required conditions to merge
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection] (documentation)
  • 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 merged commit 7ecb16b into haskell:master Jul 24, 2026
84 of 86 checks passed
@mergify mergify Bot removed the queued label Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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 release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants