Allow tagged-0.8.9

[Bodigrim]

This is currently blocking a few things on Stackage.

[andreasabel]

For instance, github.
https://github.com/commercialhaskell/stackage/blob/49d988b26269b5b18c711008ab9e0840d0268cf0/build-constraints.yaml#L6334
https://github.com/commercialhaskell/stackage/blob/49d988b26269b5b18c711008ab9e0840d0268cf0/build-constraints.yaml#L6742

[phadej]

tagged-0.8.9 is mostly relevant for GHC-9.12 support, but GHC-9.12 support is blocked on https://gitlab.haskell.org/ghc/ghc/-/issues/25653

[Bodigrim]

As I said above, my motivation has little to do with GHC 9.12. The problem is that Stackage Nightly 2025-01-15 (still on GHC 9.8) has upgraded to taged-0.8.9 and forced out anything which does not support it, primarily binary-instances and its downstream dependencies. Not having, for examples, github is really quite inconvenient.

[phadej]

It's good to know that Stackage become more aggressive with pruning packages not updating the bounds. OTOH, I barely care about Stackage and even less so about the Nightly.

[andreasabel]

@phadej wrote:

I barely care about Stackage and even less so about the Nightly.

The problem is that since matrix.hackage died, Stackage is our only centralised quality assurance for packages. So I'd say it has become more vital for the Haskell ecosystem.

[andreasabel]

There is also https://hoogle.haskell.org/ :

Hoogle is a Haskell API search engine, which allows you to search the Haskell libraries on Stackage

[phadej]

Looking at https://packdeps.haskellers.com/reverse/binary-instances I don't think not having binary-instances would make Hoogle (with stackage set) considerably worse.

I don't like that I cannot update e.g. cabal-install-parsers and some other stuff for GHC-9.12; but that is blocked on the fact that GHC-9.12.1 is broken. The tagged-0.8.8 is as good as tagged-0.8.9 in practice for everything else (there are changes in the API). Stackage curators made a bad move by not sticking with tagged-0.8.8 for time being (before they migrate Nightly to GHC-9.12).

This issue will be resolved when GHC-9.12.2 is released. If you don't like my maintenance practices, don't depend on packages I maintain.