We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hspec-2.7.10 (changelog) (Simon Hengel [email protected] @sol, Stackage upper bounds) is out of bounds for:
hspec-core-2.7.10 (changelog) (Simon Hengel [email protected] @sol, Stackage upper bounds) is out of bounds for:
The text was updated successfully, but these errors were encountered:
Add an upper bound for hspec-junit-formatter, #6024
9b4c2b8
We're good with this upper bound: the next version of hspec-junit-formatter targets that new version of hspec (#6010).
Is there anything we need to do to ensure other resolvers (e.g. nightly, next major LTS), which get that newer hspec, will also lift this bound?
Sorry, something went wrong.
Group hspec-junit-formatter's upper bound with hspec
e22b03d
We'll need to unblock them together. Related to #6024
Sounds good!
Nope, I've moved this bound closer to the previous hspec upper bound so whoever is curating stackage once it's ready can unblock both together.
hspec
Closing this due to the GHC 9 upgrade. Packages mentioned here may have been disabled, please see #6072 for more information.
No branches or pull requests
hspec-2.7.10 (changelog) (Simon Hengel [email protected] @sol, Stackage upper bounds) is out of bounds for:
hspec-core-2.7.10 (changelog) (Simon Hengel [email protected] @sol, Stackage upper bounds) is out of bounds for:
The text was updated successfully, but these errors were encountered: