Problems to add cabal-helper-1.1.0.0 to stack and cabal build plans for windows

[jneira]

• I am trying to add cabal-helper-1.1.0.0 to hie and hls (haskell-language-server)
• The package is compatible with a wide range of Cabal versions in linux but it requires Cabal >= 3.0.1 for windows to exclude versions without the stripExeExtension bug
• There is a problem with haddock-api: for versions < 2.23 it was fixing at once the upper bounds of base and Cabal, so you only can allow Cabal versions using allow-newer in stack.yaml and cabal.project
• This change is only needed for windows so it is unfortunate to have to add the dangerous allow-newer (you know for stack is equal to --skip-solver-forall-packages) for being able to update one package for one os
• It will be needed for ghc-8.4 and ghc-8.6
• Options:
  • Dont update cabal-helper for those ghc versions 😞
  • Use allow-newer for those ghc versions:
    • it will need dedicated cabal.project and stack.yaml files per ghc and windows version (up to 8 files in hie) i we want isolate allow-newer 😞
  • Backport the fix to Cabal-2.4.0.0 and 2.4.1.0 (maybe Cabal-2.2 for ghc-8.4.4?) , use those Cabal patched version and remove the lower bound for c-h in windows. This seems to be the right one but 😨
  • Remove the lower bound for windows and let the bug free 😥
    • Here is my question: how affected that bug to cabal-helper usage, there are some issues here or in any downstream packages?

[jneira]

@DanielG really good news, haddock-api had been revised in hackage and Cabal upper bound for all affected versions is ^>=2.2 || ^>=2.4 || ^>=3.0 || ^>=3.2 now

[jneira]

Thanks to the hackage revisions of haddock-api we could add cabal-helper-1.1 to both hls and hie

Thanks @DanielG for suggesting it