Skip to content

Backport #12273: Mark CabalSpecV3_18 as latest on the 3.18 branch - #12368

Open
mergify[bot] wants to merge 1 commit into
masterfrom
mergify/bp/master/pr-12273
Open

mergify[bot] wants to merge 1 commit into
masterfrom
mergify/bp/master/pr-12273

Conversation

@mergify

@mergify mergify Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Summary

  • mark CabalSpecV3_18 as the latest supported specification on the 3.18 branch
  • keep cabal-version: 3.18 Simple packages on the in-process setup path

Background

Cabal-syntax 3.18 recognizes CabalSpecV3_18, but cabalSpecLatest remained
CabalSpecV3_16. cabal-install therefore classified Simple packages that
declare cabal-version: 3.18 as future-format packages and selected an external
setup script.

Addresses #12271.

Testing

  • cabal build Cabal-syntax
  • evaluated cabalSpecLatest in the Cabal-syntax REPL and obtained
    CabalSpecV3_18

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

Cabal-syntax 3.18 recognizes CabalSpecV3_18, but cabalSpecLatest remained
CabalSpecV3_16. cabal-install consequently treated Simple packages that
declare cabal-version 3.18 as future-format packages and selected an
external setup script.

Move the supported-version boundary to CabalSpecV3_18 so these packages use
the in-process setup path.

Fixes #12271

(cherry picked from commit a290081)
@ffaf1

ffaf1 commented Sep 21, 2026

Copy link
Copy Markdown
Collaborator

Mhhh, should we have 3_18 on master or 3_20?

@zlonast

zlonast commented Sep 21, 2026

Copy link
Copy Markdown
Collaborator

Is version 3_20 pointless for now, given that no one is releasing such new packages for their repositories?
If we are going to switch to version 3_20, perhaps we should consider a full-fledged CI setup for the nightly build?

Perhaps we should release version 3_19 instead and switch to 3_20 only when the actual release happens? (That way, we could highlight the fact that these features are temporary.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cabalSpecLatest remains 3.16 in cabal-install 3.18.1.0, causing cabal-version: 3.18 Simple packages to fail

3 participants