hspec-megaparsec-2.0.0 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:
megaparsec-7.0.1 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:
New versions (compatible with megaparsec-7.0.0 & hspec-megaparsec-2.0.0) have been released:
modern-uri-0.3.0.0stache-2.0.0cue-sheet-2.0.0I'll get to MMark stuff a bit later.
mmark-0.0.6.0 released, it's compatible with Megaparsec 7mmark-ext-0.2.1.0 has been updated in revision 2 to allow modern-uri-0.3.0.0mmark-cli-0.0.4.0 released, it's compatible with Megaparsec 7 and mmark-0.0.6.0version-3.5.0 released to match.
I've updated the initial description.
Updated list:
megaparsec-7.0.1 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:
Hey! What would be the fix for this? Setting the lower bound to the version specified?
megaparsec 7 changed its API in a way that just about every user package is going to have to adapt to, so it's probably not a simple bounds bump. There's stackbuilders/inflections-hs#60 blocking this issue, but it looks like the maintainers of that package are waiting for this issue to be resolved before they merge, so apparently we're deadlocked...
@NickSeagull here's the fix I had to do for versions: https://gitlab.com/fosskers/versions/commit/9de04ad00aac47020462e465fa59485579f24f12
The megaparsec CHANGELOG is also a good place to double-check.
dotenv-0.6.0.1 and inflections-0.4.0.4 support megaparsec-7.0.1 and hspec-megaparsec-2.0.0
Here's an updated list now:
megaparsec-7.0.1 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:
process-1.6.3.0 is out of bounds for:
I am going to have to set upper bounds for both dotenv and inflections in the meantime.
@alexeyzab I can update the bounds for dotenv to use process-1.6.3.0. I saw the API of process hasn't changed.
@alexeyzab I changed the boundaries of process to process-1.6.3.0 in dotenv-0.6.0.2
@CristhianMotoche Great, thanks!
Added to the list above:
@DanBurton Sorry for being late for the party :pray: I'm planning to release tomland-0.5.0 with constraints megaparsec >= 7.0 && < 7.1 in nearest couple days (after Hacktoberfest is over).
The list as currently reported by stackage-curator:
megaparsec-7.0.3 is out of bounds for:
Hi @DanBurton, it's not clear to me why dotenv and inflections keep being marked as out of bounds. I mention this because versions with proper boundaries to solve this, are already on hackage.
@juanpaucar my mistake!
They are constrained here, which I did not notice:
https://github.com/commercialhaskell/stackage/blob/83080d236aa0effd6d64823665659b8628578930/build-constraints.yaml#L2018
Normally we would constrain them here:
https://github.com/commercialhaskell/stackage/blob/83080d236aa0effd6d64823665659b8628578930/build-constraints.yaml#L4308
No further action is needed on your part, @juanpaucar.
Thanks @DanBurton, I thought I was missing something and I didn't want to stop you folks from upgrading megaparsec :)
Thanks for letting me know @DanBurton. I just pushed an update to use the newer 7.0.x megaparsec api.
@DanBurton sorry for the delay. tomland-0.5.0 has been released to Hackage with megaparsec ^>= 7.0.1 bounds.
@ChShersh thanks! I've opened a PR (https://github.com/commercialhaskell/stackage/pull/4126) to restore tomland to stackage; it was temporarily removed to unblock megaparsec.