@@ -33,16 +33,8 @@ After doing that commit with a message like "add foo-bar" and send a pull reques
3333The continuous integration job will do some checks to see if your package's dependencies are up-to-date.
3434
3535The CI job notably doesn't compile packages, run tests, build documentation, or find missing C libraries.
36−If you want to be proactive or if CI fails, you can make sure that your package builds against the latest nightly:
37−
38−```
39−# Build from the tarball on Hackage to check for missing files
40−$ stack unpack yourpackage && cd yourpackage-*
41−# Generate a pristine stack.yaml, adding any missing extra-deps
42−$ rm -f stack.yaml && stack init --resolver nightly
43−# Build, generate docs, test, and build benchmarks
44−$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
45−```
36+If you want to be proactive or if CI fails, you can make sure that your package builds against the latest nightly.
37+See the [verify-package](https://github.com/commercialhaskell/stackage/blob/master/verify-package) script in this repository.
4638
4739This approach works well, but has two limitations you should be aware
4840of:
@@ -173,7 +165,7 @@ ending in `.0`), the package set is taken from Stackage Nightly. Therefore, by
173165following the above steps, you can get your package into the next major LTS
174166Haskell release.
175167
176−If you would like to get your package added to the current LTS Haskell
168+If you would like to get your package added to the current LTS Haskell
177169major release, please do the following in addition to the steps for Nightly described earlier:
178170
179171* Check that your package can be built with the current LTS version (e.g. `stack build --test --bench --haddock --resolver lts`)