I updated cabal-version
to 3.6
in my pkg.cabal file.
cabal-version: 3.6
And upload it to hackage results in an error:
http code 400
Error: Invalid package
'cabal-version' must be at most 3.0
I updated cabal-version
to 3.6
in my pkg.cabal file.
cabal-version: 3.6
And upload it to hackage results in an error:
http code 400
Error: Invalid package
'cabal-version' must be at most 3.0
Possibly, but what’s wrong with that? Are you using cabal
features that are only introduced in cabal
s strictly greater than 3.0
?
Yes, I use hsc2hs-options
which introduced by 3.6
Ah I see. I don’t think I can help you then. Hopefully someone who knows more about Hackage can
Yes, you are right. But hsc2hs-options
was added since 3.6
cabal file spec. My local cabal exe version is 3.8.
https://cabal.readthedocs.io/en/latest/file-format-changelog.html#cabal-version-3-6
hackage-server
refuses a cabal-version
that is too new, to prevent uploading a package which most users will not be able to compile.
This has recently been updated to cabal-version: 3.6
(see #1224), I suspect yet to be deployed.
The branch that gets deployed is the central-server branch, and its typically merged from master at the time of deploy. So once can skim the commits to see what has and hasn’t been deployed yet. Comparing central-server...master · haskell/hackage-server · GitHub