Fix typo explitic

[philderbeast]

A follow on from #11501. This changes a couple of data constructors in Cabal.

---

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
  • Is the change significant? If so, remember to add significance: significant in the changelog file.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.
• Tests have been added. (Ask for help if you don’t know how to write them! Ask for an exemption if tests are too complex for too little coverage!)

[geekosaur]

It has (finally) occurred to me to wonder if we can define bidirectional pattern synonyms with the old names for constructors like this, and mark them as deprecated so users get warnings. We might then remove them in 3.20. I won't block the PR on that, though.

[philderbeast]

define bidirectional pattern synonyms with the old names for constructors like this, and mark them as deprecated so users get warnings.

That's possible but I don't think the effort is worth it. I searched GitHub for the typo "CVExpliticDepsCustomSetup" and the only hits were in forks of haskell/cabal. Same goes searching for "CICVExpliticDepsCustomSetup". Within haskell/cabal itself, this constructor is only used within the function:

cabal/Cabal/src/Distribution/PackageDescription/Check.hs

Line 393 in 449d2ef

checkPackageDescription :: Monad m => PackageDescription -> CheckM m ()

[philderbeast]

I won't block the PR on that, though.

Thanks @geekosaur.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-03-27 13:50 UTC · Rule: default
• ✅ Checks started · on draft merge queue: embarking master (ec8052b) and #11621 together #11664
• 🚫 Left the queue — 2026-03-27 14:15 UTC · at 5fc69e7701e2fd1bb92513093765b53b15803826

This pull request spent 24 minutes 49 seconds in the queue, including 14 minutes 15 seconds running CI.

Required conditions to 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 = Bootstrap post job
  • check-skipped = Bootstrap post job
  • check-success = Bootstrap post job
• #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • Fix typo explitic #11621
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • Fix typo explitic #11621
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Fix typo explitic #11621
• 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 = 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

Failing checks:

• ❌ Bootstrap post job

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.

[geekosaur]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-03-27 14:19 UTC · Rule: default
• ✅ Checks passed · on draft merge queue: embarking master (ec8052b) and #11621 together #11665
• ✅ Merged — 2026-03-27 16:21 UTC · at 5fc69e7701e2fd1bb92513093765b53b15803826

This pull request spent 2 hours 1 minute 45 seconds in the queue, including 1 hour 50 minutes 23 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • Fix typo explitic #11621
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • Fix typo explitic #11621
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Fix typo explitic #11621
• 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

[geekosaur]

That was a new one: communication failure with the runner.