@@ -313,8 +313,6 @@ For an LTS minor bump, you'll typically want to:
314Then run `NOPLAN=1 build.sh` to build the generate an updated snapshot.
314Then run `NOPLAN=1 build.sh` to build the generate an updated snapshot.
316−This replaces `CONSTRAINTS=...' /var/stackage/stackage/automated/build.sh lts-x.y` for the old curator-1.
318If a build fails for bounds reasons, see all of the advice above. If the code
316If a build fails for bounds reasons, see all of the advice above. If the code
319itself doesn't build, or tests fail, open up an issue and then either put in a
317itself doesn't build, or tests fail, open up an issue and then either put in a
320version bound to avoid that version or something else. It's difficult to give
318version bound to avoid that version or something else. It's difficult to give
@@ -329,7 +327,7 @@ if one needs to revert one package, say due to a build or test regression,
329one can edit `current-plan.yaml` and updated the SHA256 hash of the .cabal file,
327one can edit `current-plan.yaml` and updated the SHA256 hash of the .cabal file,
330to avoid having to rebuild everything again.)
328to avoid having to rebuild everything again.)
332−_Sadly no longer true currently_: ~~Note LTS builds inherit the current Hackage data (stack updated for Nightly) to avoid excess extra rebuilding.~~
330+Note LTS builds without NOPLAN will use the latest Hackage data.
334### Timing
332### Timing