@@ -206,12 +206,11 @@ If a new package fails to build because of missing system libraries we often ask
206206
207207### Upgrading GHC version
208208The Dockerfile contains information on which GHC versions should be used. You
209−can modify it and push it to Github to trigger a DockerHub build. The nightly
209+can modify it and push it to Github to trigger a build. The nightly
210210branch is used for nightlies. For LTSes, we use the ltsX branch, where X is the
211211major version number (e.g., lts3 for lts-3.\*).
212212
213−Note that when starting a new LTS major release, you'll need to modify Docker
214−Hub to create a new Docker tag for the relevant branch name.
213+Note that when starting a new LTS major release, you'll need to modify `.github/workflows/image.yml` to add a new lts branch.
215214
216215Update `GHCVER` in `Dockerfile`. (This env var automatically gets passed to `debian-bootstrap.sh`.)
217216
@@ -241,7 +240,7 @@ docker rm $(docker ps -a -q)
241240docker rmi $(docker images -q)
242241```
243242
244−but `docker pull commercialhaskell/stackage:nightly` can also be run instead just to update the nightly image say.
243+but `docker pull ghcr.io/commercialhaskell/stackage/build:nightly` can also be run instead just to update the nightly image say.
245244
246245For a new GHC version you should also delete the ~~cache~~ .stack-work snapshot install directories on the stackage-build server to
247246~~force all packages to be rebuilt~~ clear up some space. See: [issue#746](https://github.com/commercialhaskell/stackage/issues/746). Eg:
@@ -555,8 +554,7 @@ Every 3-6 months, we make a new major release of LTS. The procedure we follow fo
555554 relaxed upper bounds. There will likely be some hard decisions to be made
556555 regarding relaxing a bound versus keeping more packages. All of these changes
557556 occur on master and affect nightly.
558−4. Once the estimated date hits, push a new `ltsXX` branch and trigger Docker
559− Hub to build a Docker image for the new release.
557+4. Once the estimated date hits, push a new `ltsXX` and wait for the docker image build.
5605585. Run the build procedure for the new LTS release.
5615596. After the LTS build completes, more aggressively prune upper bounds from
562560 `build-constraints.yaml`.