mosaicstack/stack
1
0
Fork 0
Code Issues 31 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

chore(release): mosaic CLI 0.0.41 #640

Merged
jason.woltje merged 1 commits from release/mosaic-cli-0.0.41 into main 2026-06-23 02:21:05 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
jason.woltje commented 2026-06-23 02:12:40 +00:00
Owner
Copy Link

Cuts 0.0.41, the first installable CLI that carries the CRITICAL re-seed data-loss fix (#632).

Why

0.0.40 was published before #632 landed on main (release e2336bb at 19:49 vs #632 bf2a674 at 21:38). As a result, the installed 0.0.40 CLI still has the roster-wipe bug: mosaic update / framework re-seed wipes user fleet data (roster + active units). Until 0.0.41 ships, nobody can safely run mosaic update.

What

  • Bump @mosaicstack/mosaic 0.0.40 → 0.0.41 (one line; matches how #624 cut 0.0.40).
  • No code changes — purely a version cut to publish the already-merged #632 fix.

Unblocks

Once published, the orchestrator self-seed relaunch (route orchestrator-launch.sh through mosaic yolo claude) is safe to perform — mosaic update will no longer destroy the live roster.

Cuts **0.0.41**, the first installable CLI that carries the CRITICAL re-seed data-loss fix (#632). ## Why 0.0.40 was published *before* #632 landed on main (release `e2336bb` at 19:49 vs #632 `bf2a674` at 21:38). As a result, the installed 0.0.40 CLI still has the roster-wipe bug: `mosaic update` / framework re-seed wipes user fleet data (roster + active units). Until 0.0.41 ships, nobody can safely run `mosaic update`. ## What - Bump `@mosaicstack/mosaic` `0.0.40` → `0.0.41` (one line; matches how #624 cut 0.0.40). - No code changes — purely a version cut to publish the already-merged #632 fix. ## Unblocks Once published, the orchestrator self-seed relaunch (route `orchestrator-launch.sh` through `mosaic yolo claude`) is safe to perform — `mosaic update` will no longer destroy the live roster.
jason.woltje added 1 commit 2026-06-23 02:12:41 +00:00
chore(release): mosaic CLI 0.0.41
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Details
ci/woodpecker/pr/ci Pipeline was successful
Details
ee29d0610a 
First release carrying the CRITICAL re-seed data-loss fix (#632):
`mosaic update` / framework re-seed now preserve user fleet data
(roster + active units) instead of wiping them. 0.0.40 shipped before
#632 landed, so 0.0.41 is the first installable CLI safe to run
`mosaic update` against.
jason.woltje merged commit a38a491403 into main 2026-06-23 02:21:05 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#640
Delete Branch "release/mosaic-cli-0.0.41"

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?