Skip to content

Backport #12346: Changelogs 3.18.2.0 - #12361

Merged
mergify[bot] merged 1 commit into
masterfrom
mergify/bp/master/pr-12346
Sep 17, 2026
Merged

mergify[bot] merged 1 commit into
masterfrom
mergify/bp/master/pr-12346

Conversation

@mergify

@mergify mergify Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor
  • Patches conform to the coding conventions.
  • no Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

This is an automatic backport of pull request #12346 done by [Mergify](https://mergify.com).

* Add changelogs for 3.18.2.0

* Remove changelog files for 3.18.2.0

(cherry picked from commit a14e7af)
@mergify mergify Bot mentioned this pull request Sep 15, 2026
2 tasks
@mergify mergify Bot added the backport label Sep 15, 2026
@mergify mergify Bot added the ready and waiting Mergify is waiting out the cooldown period label Sep 15, 2026
@mergify mergify Bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels Sep 17, 2026
@mergify

mergify Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor Author

Merge Queue Status

  • Entered queue2026-09-17 14:20 UTC · Rule: default · triggered by rule Put pull requests in the rebase+merge queue
  • Checks skipped · PR is already up-to-date
  • Merged2026-09-17 14:31 UTC · at aeb7dbfabad38289cb36da6fdf78acee99b69e3b · merge

This pull request spent 11 minutes 23 seconds in the queue, including 9 seconds running CI.

Required conditions to 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

@mergify
mergify Bot merged commit aeb7dbf into master Sep 17, 2026
77 checks passed
@mergify
mergify Bot deleted the mergify/bp/master/pr-12346 branch September 17, 2026 14:31
@mergify mergify Bot removed the queued label Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants