@@ -382,6 +382,9 @@ will upgrade their packages to allow for the new GHC release.
382We prefer to prune packages causing upper bounds constraints **after** the LTS
382We prefer to prune packages causing upper bounds constraints **after** the LTS
383release to allow the maximum amount of packages to get into the newest LTS.
383release to allow the maximum amount of packages to get into the newest LTS.
385+You will almost always need to update the Win32 package version listed in the
386+build-constraints.yaml file.
385After the first LTS release, the package pruning process may begin in the
388After the first LTS release, the package pruning process may begin in the
386nightly build in order to move forward with getting the latest versions of
389nightly build in order to move forward with getting the latest versions of
387packages compatible with the new GHC release.
390packages compatible with the new GHC release.