@@ -29,13 +29,12 @@ The CI job notably doesn't compile packages, run tests, build documentation, or
29If you want to be proactive or if CI fails, you can make sure that your package builds against the latest nightly:
29If you want to be proactive or if CI fails, you can make sure that your package builds against the latest nightly:
32−$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
32+# Build from the tarball on Hackage to check for missing files
33−```
33+$ stack unpack yourpackage && cd yourpackage-*
34−
34+# Generate a pristine stack.yaml, adding any missing extra-deps
35−Or, if some dependencies haven't made it into Stackage Nightly yet:
38$ rm -f stack.yaml && stack init --resolver nightly --solver
35$ rm -f stack.yaml && stack init --resolver nightly --solver
36+# Build, generate docs, test, and build benchmarks
37+$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
41Or, alternatively, with `cabal` (may end up using older dependency
40Or, alternatively, with `cabal` (may end up using older dependency