on master help sign in
CURATORS: bump Win32 when updating ghc version
aa8140fJens Petersen
CURATORS.md+2
@@ -210,6 +210,8 @@ can modify it and push it to Github to trigger a build. The nightly
210branch is used for nightlies. For LTSes, we use the ltsX branch, where X is the
210branch is used for nightlies. For LTSes, we use the ltsX branch, where X is the
211major version number (e.g., lts3 for lts-3.\*).
211major version number (e.g., lts3 for lts-3.\*).
212
212
213+Update the `Win32` version in `build-constraints.yaml` under "GHC upper bounds".
214+
213Note that when starting a new LTS major release, you'll need to modify `.github/workflows/image.yml` to add a new lts branch.
215Note that when starting a new LTS major release, you'll need to modify `.github/workflows/image.yml` to add a new lts branch.
214
216
215Update `GHCVER` in `Dockerfile`. (This env var automatically gets passed to `debian-bootstrap.sh`.)
217Update `GHCVER` in `Dockerfile`. (This env var automatically gets passed to `debian-bootstrap.sh`.)