You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2026.9.29.3: a program shipped through artifacts in a workspace plan waits for no plan-level runtime file, and its own runtime files are beside it
The validation project's post-release build of 2026.9.29.2 stopped with
"'bin/translations/qt_gppcli_en.qm', needed by 'obj/gpp_updater/Updater.exe',
missing and no known rule to make it".
- The link edge of a unit outside the link groups (a program shipped through
artifacts) no longer takes the plan's deploy set as order-only inputs in a
workspace plan: the virtual root has no program, and nothing places that set.
- A member's runtime set includes the closure of every package whose program
the member ships through artifacts, so the program's own runtime files are
in the member's product directory, as they were beside a root's program.
- e2e 833 G9 states both; G2 and G3 count compile and link outputs, since a
plan of another selection stages the runtime files again.
- Version 2026.9.29.3; design document section 17.1.
Copy file name to clipboardExpand all lines: .agents/docs/2026-09-29-workspace-build-graph-design.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -558,6 +558,7 @@ read from the member, or made a value of the plan:
558
558
|`[build] linkage`| not copied to the virtual root | a root-position value | unit `RootPositionValuesSeparateMembers`|
559
559
| unknown `mcpp:` capability, cfg() and schema warnings | not reported for a member | refused and reported for each selected member | e2e 836 M2, M3 |
560
560
| the shared libraries of a member's closure | only those the member's units link were placed | every graph-built shared library of the closure, with its aliases, as §15 states | e2e 835 L3 |
561
+
| the runtime files of a program shipped through `artifacts` (2026.9.29.3) | its link waited for the plan's deploy set, which a workspace plan does not place; its own runtime files were not in the member's directory | the link waits for no plan-level file; a member's runtime set includes the closures its `artifacts` edges reach | e2e 833 G9 |
561
562
562
563
Each criterion fails on 2026.9.29.1 and passes on 2026.9.29.2. The resource
563
564
case also showed a defect of every build: a quoted `#include` in a script was
0 commit comments