|
83 | 83 | # phase -- and `mcpp-package.json` beside every staged tree, which |
84 | 84 | # `mcpp::plugins::package` reads. Until that release exists the jobs build it |
85 | 85 | # from `MCPP_SOURCE_REF` (the repository variable names the branch). |
| 86 | + # |
| 87 | + # 2026.11.7.1 IS WHAT 0.21.0'S CMAKE CROSS LANE NEEDS (mcpp#885): the engine |
| 88 | + # completes a cross subproject's contract (its compilers, archiver and target) |
| 89 | + # when the action runs, which a subproject that links an executable or a |
| 90 | + # shared library needs. The package floor stays 2026.10.30.1: every other |
| 91 | + # member, and a cross subproject that only builds archives, works on the |
| 92 | + # older engine, and docs/deps.md states the requirement where cross builds |
| 93 | + # are described. So here, as for 0.20.0's SYCL lane, `MCPP_VERSION` is the |
| 94 | + # newest engine a lane needs and the floor the oldest the collection loads on. |
86 | 95 | MCPP_VERSION: 2026.11.7.1 |
87 | 96 | # THE RELEASE EVERY JOB FETCHES, WHICH IS NOT ALWAYS THE ONE UNDER TEST. |
88 | 97 | # |
89 | | - # `MCPP_VERSION` states the engine this collection needs -- the package floor |
90 | | - # (`[package] mcpp`) is the same statement -- and a release of it may not exist |
| 98 | + # `MCPP_VERSION` states the engine this collection's lanes need -- the package |
| 99 | + # floor (`[package] mcpp`) the oldest it loads on -- and a release of it may not exist |
91 | 100 | # yet: 0.19.0 was written against mcpp#755 and pinned 2026.10.1.3 before that |
92 | 101 | # release was published. Every fetch therefore names this variable instead, and |
93 | 102 | # the dispatch input `mcpp_source_ref` builds the engine under review with it. |
|
0 commit comments