on master help sign in
Add new packages to constraints, not snapshot-incomplete
commitc9240400cc64770504413faa60f366d3c745ac69 authorMichael Snoyman <michael@snoyman.com> dateWed 12 Feb 2020, 08:46 (7 years ago) parent54f31e2
2 files changed+2−2
CURATORS.md+1−1 automated/build.sh+1−1
CURATORS.md+1−1
@@ -299,7 +299,7 @@ First run `build-next.sh` to regenerate updated `ltsXX/work/constraints.yaml` an
299299For an LTS minor bump, you'll typically want to:
300300
301301* Add constraints to package `range:` fields _under_ the `source:` field in that `constraints.yaml`.
302−* Add new packages versioned to `snapshot-incomplete.yaml` (the `@<hash>` suffix is optional)
302+* Add new packages to the `constraints.yaml` file
303303* 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.
304304
305305Then run `NOPLAN=1 build-next.sh` to build the generate an updated snapshot.
automated/build.sh+1−1
@@ -107,7 +107,7 @@ then
107107 docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "curator update && curator constraints --target $TARGET && curator snapshot-incomplete --target $TARGET && curator snapshot"
108108 fi
109109else
110− docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "curator snapshot"
110+ docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "curator snapshot-incomplete --target $TARGET && curator snapshot"
111111fi
112112
113113