CURATORS: emphasize that range must be put under source

Otherwise constraints are just ignore and will be breakage will reappear on the next build-next.sh without NOPLAN
This commit is contained in:
Jens Petersen 2020-01-28 11:03:26 +08:00 committed by GitHub
parent db3f6b70bc
commit e9b227bbf8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -298,7 +298,7 @@ First run `build-next.sh` to regenerate updated `ltsXX/work/constraints.yaml` an
For an LTS minor bump, you'll typically want to:
* Add constraints to package `range:` fields in that `constraints.yaml`.
* Add constraints to package `range:` fields _under_ the `source:` field in that `constraints.yaml`.
* Add new packages versioned to `snapshot-incomplete.yaml` (the `@<hash>` suffix is optional)
* Test, benchmark, haddock failures can also be added to package fields in the `constraints.yaml` if necessary, though it should be avoided if possible for LTS.