Cabal & cabal-install 3.10.2.0 release list

[Kleidukos]

The machine never stops.

3.10.2.0 is a patch release destined to cement the 3.10 series as the recommended cabal version in toolchain managers

See: cabal-install 3.10.2.0 board

Here are the bullet points for releasing 3.10.2.0 for Cabal & cabal-install.

Tasks

• Changelogs (Add changelogs for 3.10.2.0 #9207)
• Upload candidates
  • Cabal
  • Cabal-syntax
  • cabal-install
  • cabal-install-solver

Cabal

• Version bump (see Update Cabal{,-install,-syntax} to 3.10.2.0 #9033)
• Do not check PVP on internal targets (backport of #9004 to 3.10) #9013
• Revert workaround to filter JavaScriptFFI out on GHC versions where G… (backport #8979) #9029
• use with compiler flags in key of cached project config (backport #8819) #9027
• Return empty default when git fails (backport #8755) #9032
• check: allow "haiku" as a valid OS string. #9048
• Do not always pass --quickjump to haddock (backport #9049) #9073
• Bump deepseq bounds to allow 1.5 (backport #9078) #9093
• Support GHC 9.8 in cabal 3.10.2.0 #9225
• PD check: do not treat library names as package names (backport #9132) #9145

cabal-install

• Version bump (see Update Cabal{,-install,-syntax} to 3.10.2.0 #9033)
• Do not check PVP on internal targets (backport of #9004 to 3.10) #9013
• Add Distribution.Client.Main (backport #8793) #9031
• Document the pkg: prefix for package targets (backport #9015) #9079
• cabal-install: Fix non-reinstallable package set (backport #9092) #9141
• Fix overzealous warnOnTwoConfigs (backport #9278) #9283

Cabal-syntax

• Version bump (see Update Cabal{,-install,-syntax} to 3.10.2.0 #9033)

[jessicah]

Can #9006 get added to the list please? :)

[fgaz]

@jessicah this is a patch release so we can't backport that, sorry. It will be in 3.11 3.12 though :)

[ulysses4ever]

3.12 rather, but yeah that's right. 3.12 should appear with GHC 9.8 late summer / early fall i think

[jessicah]

@fgaz ah right, the new value in the OS type. When is late summer / early fall? It's blocking other pull requests I have due to CI failures with hackage not recognising Haiku as a valid OS value.

• haiku: add as known platform hackage-server#1217
• haiku: depends on libnetwork network#561
• haiku: use libstdc++ text#521

And a couple more I have in the pipeline (resolv, directory).

[Mikolaj]

@Kleidukos: how about #8952?

[Mikolaj]

@Kleidukos: another candidate, this one hacky, but urgent: #9048

[Kleidukos]

Regarding #8952 we just have to wait for it to be merged, for the backport to be created.
Regarding #9048 I have no problems but I'd like confirmation from @gbaz that an upgrade of hackage central can be done shortly, before approving the cabal PR.

[jessicah]

@Kleidukos as stated elsewhere, the hackage PR doesn't appear to be strictly necessary to deploy the cabal check commit. I was able to upload packages to a test deploy without that PR merged.

[nmeum]

What's the progress on this? It seems that all TODOs in the issue description have been resolved but on Hackage 3.10.2.0 is still a package candidate. I maintain an Alpine Linux package for Cabal and I am currently wondering if we should update from 3.10.1.0 to 3.10.2.0.

[Kleidukos]

@nmeum Right now we're here: haskell/ghcup-metadata#116

If you have an i386 Alpine system we would use a hand to create bindists (executable + plan.json).