Fix reusable release

[ffaf1]

This should fix #12371.
I have tested this for Win, but not for FreeBSD as I do not have a runner available.
If anyone knows how to test on FreeBSD, let me know.

---

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

[ulysses4ever]

🙏

[Mikolaj]

Phew. That could have gone worse. Well done.

[Mikolaj]

Any more reviews please? If not, shall we mark it high priority?

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-09-26 05:16 UTC · Rule: squash-merge · triggered by rule Put pull requests in the squash+merge queue
• ✅ Checks passed · on draft merge queue: checking #12372 on master (773c039) #12377
• ✅ Merged — 2026-09-26 06:59 UTC · at ca85b6dc7d2a1404e45429c7a73c83a4ea885219 · squash

This pull request spent 1 hour 43 minutes 10 seconds in the queue, including 1 hour 32 minutes 22 seconds running CI.

Required conditions to merge

• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Fix reusable release #12372
• github-review-approved [🛡 GitHub branch protection]
  • Fix reusable release #12372
• 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

[zlonast]

@mergify backport 3.18

[mergify]

backport 3.18

✅ Backports have been created

Details

• #12379 Backport #12372: Fix reusable release has been created for branch 3.18 but encountered conflicts

Cherry-pick of ca85b6d has failed:

On branch mergify/bp/3.18/pr-12372
Your branch is up to date with 'origin/3.18'.

You are currently cherry-picking commit ca85b6d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/reusable-release.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally