cabal bump versions (`master`)

Don't merge this until after the 3.16 branch is cut: it needs different version bumps. It also needs the hackage-security revision to go in and the index state re-pinned.

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

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

Depends-on: #11024

Jun 25 '25 17:06 geekosaur

Who did the symbolic paths change to Cabal? You missed the custom-setup in cabal-testsuite. (More correctly, it couldn't be done then because we had to run that against 3.12.1.0; it is only now being run against 3.14.1.1.) See https://github.com/haskell/cabal/actions/runs/15889545297/job/44809267322?pr=11022#step:10:520 for details.

/cc: @sheaf

Jun 26 '25 00:06 geekosaur

For the time being, since it only involves the test suite's custom setup, I've reverted that and the matching validate.yml dependency to 3.12.1.0.

Jun 26 '25 00:06 geekosaur

Wait, we should be getting the new hackage-security at this point?

ETA: missing from release wiki page: need to regenerate jsons after the new hackage-security is released, or it'll bootstrap using the old version

Jun 26 '25 01:06 geekosaur

Forgot I need to move the splitmix constraint to the right place so all the project files get it, not just the one needed for validate to work. Probably need to regenerate the jsons again since I think we make one for Macs too?

Jun 26 '25 14:06 geekosaur

I see only linux jsons.

Jun 26 '25 15:06 ulysses4ever

But we nevertheless have a macos bootstrap job. I guess it uses one of the Linux jsons?

Jun 26 '25 15:06 geekosaur

Did I do it wrong? Now bootstrap is trying to download buildinfo-reference-generator-0, which I'm pretty sure is internal?

ETA: and indeed the new jsons reference it, but the old ones didn't. Anyone know what's going on here?

ETA: regenerating them again got rid of it. No clue… Nope, I made a dumb git mistake, it's still happening on this branch for some reason. Okay, I pulled in one too many imports to cabal.bootstrap.project. Fixed now.

Jun 26 '25 15:06 geekosaur