Skip to content

Conversation

@ffaf1
Copy link
Collaborator

@ffaf1 ffaf1 commented Nov 12, 2025

Include the following checklist in your PR:

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

geekosaur and others added 21 commits July 3, 2025 15:45
This commit is directly to 3.16 branch.

Note that I discovered two missed version bumps on `master` which
must be addressed in a separate PR.
…sion-numbers

adjust versions for 3.16.0.0 release
(cherry picked from commit 34e7e62)
Co-authored-by: Phil de Joux <philderbeast@gmail.com>
(cherry picked from commit 0436a81)
* Add changelog files for 3.16

* Integrate Brandon’s suggestions.
* Integrate Brandon’s suggestions /II.
* Integrate Bodigrim’s suggestions.
* Integrate Artem’s suggestions.
  * Correctly capitalize “AArch” in preparation of haskell#11047 backport
* Integrate Artem’s suggestions /II.

* Remove changelog.d bits
Also bumps the cabal-install used during the release process to
3.14.2.0.

(cherry picked from commit e727299)
* Drop deb9, ubuntu18 and centos7 jobs which are all EOL
* Add ubuntu24_04
* Build a very old alpine bindist (3.12) and a new one (3.20)
* Only build 3_20 bindist for alpine i386.

The list of release platforms after this commit is

Linux

* x86_64
  - deb10
  - deb11
  - deb12
  - fedora33
  - fedora36
  - fedora38
  - rocky8
  - ubuntu20_04
  - ubuntu22_04
  - ubuntu24_04
  - alpine3_12
  - alpine3_20
* i386
  - deb10
  - alpine3_20
* aarch64
  - deb10
  - deb11
  - deb12
  - alpine3_18

Darwin
* x86_64
* aarch64

Windows
* x86_64

(cherry picked from commit 976e0f9)
Backport haskell#11032: Update release CI scripts (boot compiler and platform support)
…al files (haskell#11063)

* missed all the copyrights in the cabal files

(cherry picked from commit 7f494c2)

# Conflicts:
#	Cabal-hooks/Cabal-hooks.cabal
#	Cabal-syntax/Cabal-syntax.cabal
#	Cabal/Cabal.cabal

* Update Cabal-hooks/Cabal-hooks.cabal

* Update Cabal-syntax/Cabal-syntax.cabal

* Update Cabal/Cabal.cabal

---------

Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: Mikolaj Konarski <mikolaj@well-typed.com>
We recently changed Cabal to use response files for all GHC arguments by
default.
Unfortunately, this broke a couple of downstream consumers of cabal,
notably Haskell Language Server and doctest, which both assume that
`--interactive` is the first argument of the `ghc` invocation by
`cabal repl`.

This regression was fixed by implementing the `--with-repl` (haskell#9115)
argument, and tools, such as hie-bios and doctest, have been updated to
take advantage of this. However, this renders already published HLS
binaries, so any HLS version <=2.12.0.0, incompatible with `cabal-3.16`,
as these old binaries can't be easily updated.

In other words, no released HLS binary (at the point of this commit), is
compatible with the cabal-3.16.0.0. Users have to build HLS from source
to have a working toolchain.

To give us a slightly better migration window, we undo some of the
improvements to cabal, and make sure that `--interactive` is always
passed as the first argument to the underlying `ghc` invocation.
This hack is supposed to be temporary, and removed for cabal 3.18.

Further, we don't use response files for the final `ghc --interactive`
invocation.
…e-first-argument-3.16

Always pass '--interactive' as the first ghc argument
(cherry picked from commit 9d8968e)
So people don't have to open all of the collapsed test output to find
any failures.

(cherry picked from commit e93d9c0)
Backport haskell#11242: indicate which of the joined tests failed
@ffaf1 ffaf1 added the backport label Nov 12, 2025
@ffaf1 ffaf1 closed this Nov 12, 2025
@mergify
Copy link
Contributor

mergify bot commented Nov 12, 2025

⚠️ The sha of the head commit of this PR conflicts with #11280. Mergify cannot evaluate rules on this PR. ⚠️

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.

5 participants