Phase B1: bring next current with main (merge + resolve conflicts) #1040

Closed
opened 2026-08-03 08:15:59 +00:00 by coder-mos1 · 0 comments
Collaborator

Bring the next prerelease lane current with main (it is 152 commits behind and ships the OLD ci-queue-wait guard 273/0), while preserving next's 10 in-flight commits.

Deliverable: merge main→next with the 8 content conflicts resolved (gateway command-executor/session-gc/cron/system-override, package.json, finalize.ts, install.sh, defaults README), guard restored to 482/5, next's 10 in-flight commits intact. On merge, next self-versions 0.0.50-next on the next dist-tag (never latest).

Delivered by PR #1039. Feature graduation of next's 10 commits to main is separate (Phase B2, #1037).

Bring the `next` prerelease lane current with `main` (it is 152 commits behind and ships the OLD ci-queue-wait guard 273/0), while preserving next's 10 in-flight commits. Deliverable: merge main→next with the 8 content conflicts resolved (gateway command-executor/session-gc/cron/system-override, package.json, finalize.ts, install.sh, defaults README), guard restored to 482/5, next's 10 in-flight commits intact. On merge, next self-versions 0.0.50-next on the `next` dist-tag (never `latest`). Delivered by PR #1039. Feature graduation of next's 10 commits to main is separate (Phase B2, #1037).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1040