You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 3, 2024. It is now read-only.
haddock-api was fixing both base' and Cabal` package versions
It makes difficult to use it in build plans that needs a newer Cabal version compatible with an older base one
The problem has arised when we tried to use cabal-helper-1.1.0.0 in haskell-ide-engine, that uses in turn haddock-api for several builds plans for ghc >= 8.4.2 and <= 8.6.5
cabal-helper needs Cabal > 3.0.1.0 in windows to avoid a nasty bug
haddock-api restricts upper bound on Cabal for each base/ghc version
The temporary workaround had been enable allow-newer in stack.yaml and cabal.project files
It seems that the usage of Cabal in haddock-api is not extensible and in fact allow-newer does not throw any compile error, so maybe no code patch is needed
So publish hackage revisions for those haddock-api versions relaxing the upper bound up to 3.0.1.0 could let users remove the always dangerous allow-newer