It was recently updated
criterion-1.2.0.0 is out of bounds for:
Fixed in bench-1.0.4
Fixed in dictionaries-0.2.0.2
Worth re-checking this wrt #2542
After #2542:
criterion-1.2.0.0 is out of bounds for:
New revisions published for:
JuicyPixels-extraidenticonmegaparsecstachetext-metricsvectortiles fixed.
Thanks for the notice. case-insensitive, lifted-base and scientific are fixed.
For the record, I'm going to maintain my packages' benchmark suites only when there's already another reason to make a new release as I see no benefit to inflate the package index with revisions for no good reason, and just for an optional component which doesn't even affect the install plan solving anyway (and moreover, we may soon have independent per-component solving, so there'll be even less need to keep components solvable with a shared install-plan).
superbuffer fixedI've updated the .cabal file for clash-prelude-0.11.2 on hackage with the correct bounds
I join @hvr. Please ignore the dependency check of the Test and Benchmark suites of my packages.
I also agree with @hvr
Is there an issue open for that? Doesn't seem like there's an issue open for discussing that. It seems like a sensible idea.
If you would like us to skip building your packages' tests and/or benchmarks, you can open a PR that adds your packages to the skipped-tests and skipped-benchmarks sections of build-constraints.yaml.
Closing in favor of #2604 as there is a new version of criterion released
Most helpful comment
If you would like us to skip building your packages' tests and/or benchmarks, you can open a PR that adds your packages to the
skipped-testsandskipped-benchmarkssections of build-constraints.yaml.See: https://github.com/fpco/stackage/blob/8b5f88c12566a1e2588748b6114ba12d89d752d9/build-constraints.yaml#L3767