Skip to content

Update cabal-version to 3.14 - #5020

Open
Aster89 wants to merge 1 commit into
haskell:masterfrom
Aster89:update-cabal-version
Open

Update cabal-version to 3.14#5020
Aster89 wants to merge 1 commit into
haskell:masterfrom
Aster89:update-cabal-version

Conversation

@Aster89

@Aster89 Aster89 commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Attempt at updating cabal-version to 3.14.

The real motivation is to have the extra-files stanza in which to move most files currently listed under extra-source-files; doing so would improve the developer experience by preventing cabal run/build from rebuilding the project when only */testdata/* files are changed.

@Aster89
Aster89 force-pushed the update-cabal-version branch from 2e26c8d to d2fca21 Compare July 21, 2026 05:30
@fendor

fendor commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator

Looks like stackage lts23 doesn't support building with Cabal-3.14.

The lts23 is quite old, so I think we can argue that we should upgrade the snapshot. We can probably drop that lts version or upgrade it to https://www.stackage.org/lts-23.28, to bump to GHC 9.8. GHC 9.6 will be dropped after the next release, so I think it is fine to not test it in CI with stack any more.

The failures with cabal are caused by old ormolu versions. I don't think we can simply force a newer ormolu version. In https://github.com/haskell/haskell-language-server/blob/master/haskell-language-server.cabal#L1454C1-L1454C63, we see

    , ormolu          ^>=0.5.3 || ^>= 0.6 || ^>= 0.7 || ^>=0.8

I doubt we actually support ^>=0.5.3 || ^>= 0.6 but https://hackage.haskell.org/package/ormolu-0.7.7.0 only works with Cabal-syntax (>=3.12 && <3.13), and ghc-lib-parser (>=9.10 && <9.11). So that sounds like an issue.
To be sure, I am unsure, but it looks like the GHC 9.10 CI might have succeeded, so maybe there is some more wiggle room.

TL;DR, this PR can't be merged right away until we manage to upgrade the ormolu version to 0.8 which only works for GHC >=9.12.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants