20250818 dependency updates

[michaelwebb76]

No description provided.

[michaelwebb76]

@JackKelly-Bellroy I realised that the bytestring dependency was the only thing forcing this not to be compatible with 9.12. Is this just a metadata update in Hackage? Or does this warrant a new release?

[JackKelly-Bellroy]

@JackKelly-Bellroy I realised that the bytestring dependency was the only thing forcing this not to be compatible with 9.12. Is this just a metadata update in Hackage? Or does this warrant a new release?

Why is bytestring causing an incompatibility here? The problem to me looks like the extremely strict == depends; I'd use ^>= dependencies instead.

[michaelwebb76]

@JackKelly-Bellroy Worked. Is this another release or just a metadata update?

[JackKelly-Bellroy]

You have made no code changes since the last release, so a metadata revision will do the trick.

[michaelwebb76]

I'd like to understand the mechanics of this a little better so I can stop asking questions like this. I don't understand how it's fine to make metadata revisions when I would have thought that cabal's process is downloading the source inclusive of the cabal file that was uploaded to Hackage, so having mismatches between the uploaded cabal file and Hackage's metadata would cause real problems. Obviously that's not the case, so my model is wrong.

[JackKelly-Bellroy]

Metadata revisions are stored on Hackage as additional .cabal files next to the release tarball of that version. The tarball is not affected. cabal is smart enough to check for and download the revised package description (which is only allowed to change in certain limited ways [mostly dependency bounds]) and sub it into the build directory.

https://github.com/haskell-infra/hackage-trustees/blob/master/revisions-information.md#hackage-metadata-revisions--what-they-are-how-they-work

[michaelwebb76]

Ah great thanks for the link