tasty-1.4.0.1 (Roman Cheplyaka roma@ro-che.info @feuerbach, Stackage upper bounds) is out of bounds for:
Currently waiting on the following build dependencies:
As soon as the above packages update, we can disable the test suites for all packages below so that tasty-1.4 can be included in Stackage proper. After this, each of the following test suites can be re-enabled once they're compatible with tasty-1.4 once again.
Currently waiting on the following test-suite dependencies:
fixed safe-json with new 1.1.1.1 release
Is there a timeline for this? There seem to be an incompatibility between tasty 1.4 and tasty-expected-failure (which hakyll-convert uses in the test suite), so I can't bump the bound right now. Depending on how soon Stackage plans to move to tasty 1.4, I can either release a new version of hakyll-convert with those tests conditionally disabled, or can we just wait for the incompatibility to be sorted out?
@Minoru fair question - hard to say right now for me - we might move straight to 1.4 when we move to ghc-9.0 perhaps?
To me the first step seems to be tasty-1.3 but I am not very familiar with tasty.
STMonadTrans 0.4.5 is compatible with tasty 1.4
tasty-dejafu-2.0.0.7 done
Published dbus-1.2.17
Fixed JuicyPixels-blurhash-0.1.0.3 with Hackage metadata revision to relax upper constraint (breaking changes did not affect the library's usage).
aur and aura updated with Hackage Revisions.
lukko-0.1.1.3 now supports tasty-1.4; for the moment I've restricted the version to < 0.1.1.2 but if we want to pull in tasty-1.4 we can just disable the test suite.
hakyll-convert-0.3.0.3@rev:2 now supports tasty-1.4, but also requires tasty-expected-failure >= 0.12.2, while Stackage Nightly 2021-01-10 contains 0.11.1.2.
dhall (& co.) have been updated (cf. https://github.com/dhall-lang/dhall-haskell/commit/97b8f87109edba5b48e53d18beb47d6b1b859b17#diff-9ad05f2b2cd2f090f79195cc6b11782d763168fab6db01815a5e57e2275d511a)
I've revised tasty-wai
Released tasty-ant-xml-1.1.8
Released tasty-lua-0.2.3.2