Repository navigation
CI: split Build / Test / Pack(+Release) into discrete stages #324
Description
Today CI runs dotnet fallout Test Pack as one step. Split into discrete Build → Test → Pack(+Release) stages/targets so:
experimentalcan do build + unit-test only cheaply (then push GH Packages),- failures are attributable (compile vs test vs pack),
- pack/publish is its own gated stage.
Structural — coordinate with the 3-tier realignment.
Activity
ci: realign triggers to the 3-tier ladder + hygiene (milestone #18) (#…
ci: test before publishing on every lane + cache restore-keys (#324, #…
chore: forward-port main → experimental (CI hygiene #322/#324/#329) (#…
ChrisonSimtian commentedon May 31, 2026
Partial: test-before-publish landed on all lanes (#331). Discrete per-CI-step Build/Test/Pack intentionally NOT split — NUKE re-runs the dependency graph per
dotnet falloutinvocation (double-compile), so a singleTest PackIS the staged build. Leaving open only if a true job-per-target split (artifact handoff) is still wanted; otherwise closeable.