feat(installer): add next integration lane #686
Reference in New Issue
Block a user
Delete Branch "feat/installer-next-lane"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
tools/install.sh --next/MOSAIC_NEXT=1prerelease source-build lane targetingnext--ref/MOSAIC_REFprecedence over the next laneVerification
bash -n tools/install.shkoalaman/shellcheck)--next,--ref,MOSAIC_NEXT,MOSAIC_REFpnpm typecheckpnpm lintpnpm format:checkCloses #8
REVIEW-OF-RECORD — APPROVE (#686, head
3a5c12a539). I reviewed the installer --next lane source/docs and found no blockers.Installer behavior:
--nextsets source-build mode (FLAG_DEV=true) and targetsGIT_REF=nextonly when no explicit ref is present. Explicit refs win in both argument orders:--next --ref feature-xand--ref feature-before --nextboth display the explicit ref with "--next requested, explicit ref wins". Env parity is present:MOSAIC_NEXT=1mirrors--next, whileMOSAIC_REFwins over it. Source display lines correctly distinguish the pure next lane from explicit-ref override cases.Docs: the top installer flag/env block documents
--nextandMOSAIC_NEXT; README, framework defaults README, and user guide accurately describe the three lanes: stable npm@latest+ main framework, prerelease--nextsource build fromnext, and contributor--dev --ref Xsource build. The npm@nextdist-tag pipeline note is clearly markedPLANNED / not yet built, so it does not imply current behavior.Reviewer verification on head
3a5c12a5:bash -n tools/install.shpass; ShellCheck pass; precedence smokes pass for--next,--next --ref,--ref --next,MOSAIC_NEXT=1, andMOSAIC_NEXT=1 MOSAIC_REF=...;pnpm typecheckpass (41/41);pnpm lintpass (23/23);pnpm format:checkpass. PR CI reported green on pipeline 1626. APPROVE.