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 #632bf2a674 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.
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
e2336bbat 19:49 vs #632bf2a674at 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 runmosaic update.What
@mosaicstack/mosaic0.0.40→0.0.41(one line; matches how #624 cut 0.0.40).Unblocks
Once published, the orchestrator self-seed relaunch (route
orchestrator-launch.shthroughmosaic yolo claude) is safe to perform —mosaic updatewill no longer destroy the live roster.