fix(update): re-seed framework on version drift, not just in-command updates (#642) #646

jason.woltje · 2026-06-24T04:09:25Z

jason.woltje commented

2026-06-24 04:09:25 +00:00

Summary

mosaic update only re-seeded ~/.config/mosaic when the @mosaicstack/mosaic package was upgraded within that same command. When the CLI is upgraded another way — a direct npm i -g @mosaicstack/mosaic, or an update run where only sibling packages were outdated — the framework files (launchers, runtime adapters, fleet tools) silently stayed stale, so shipped fixes never activated. Worse, the "all packages up to date" branch returned before any re-seed could run, so a drifted-but-current host had no path to reconcile. (#642)

Fix

Add framework drift detection: compare the on-disk schema version (~/.config/mosaic/.framework-version) against the version bundled in the installed package (FRAMEWORK_VERSION in the bundled install.sh). mosaic update now re-seeds when the mosaic package updated OR the on-disk framework is older than bundled — including from the up-to-date branch.

Detection is conservative: if either version can't be read it reports no drift, so a missing/unreadable version file never triggers an unexpected re-seed. --no-reseed still opts out. The re-seed + unit-refresh + relaunch sequence is factored into one local helper shared by both paths (no behavior change to the existing path beyond also firing on drift).

New helpers (exported + unit-tested)

readInstalledFrameworkVersion / readBundledFrameworkVersion
checkFrameworkDrift → { drifted, installed, bundled }

Verification

tsc --noEmit clean · eslint clean · vitest 17/17 in update-checker.reseed.spec.ts (8 new drift cases: older/equal/newer/unreadable) · tsc build clean.

🤖 Generated with Claude Code

## Summary `mosaic update` only re-seeded `~/.config/mosaic` when the **@mosaicstack/mosaic** package was upgraded *within that same command*. When the CLI is upgraded another way — a direct `npm i -g @mosaicstack/mosaic`, or an update run where only sibling packages were outdated — the framework files (launchers, runtime adapters, fleet tools) silently stayed stale, so shipped fixes never activated. Worse, the **"all packages up to date"** branch returned *before* any re-seed could run, so a drifted-but-current host had no path to reconcile. (#642) ## Fix Add **framework drift detection**: compare the on-disk schema version (`~/.config/mosaic/.framework-version`) against the version bundled in the installed package (`FRAMEWORK_VERSION` in the bundled `install.sh`). `mosaic update` now re-seeds when the mosaic package updated **OR** the on-disk framework is older than bundled — **including from the up-to-date branch**. Detection is **conservative**: if either version can't be read it reports no drift, so a missing/unreadable version file never triggers an unexpected re-seed. `--no-reseed` still opts out. The re-seed + unit-refresh + relaunch sequence is factored into one local helper shared by both paths (no behavior change to the existing path beyond also firing on drift). ## New helpers (exported + unit-tested) - `readInstalledFrameworkVersion` / `readBundledFrameworkVersion` - `checkFrameworkDrift` → `{ drifted, installed, bundled }` ## Verification `tsc --noEmit` clean · eslint clean · `vitest` 17/17 in `update-checker.reseed.spec.ts` (8 new drift cases: older/equal/newer/unreadable) · `tsc` build clean. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jason.woltje added 1 commit 2026-06-24 04:09:26 +00:00

fix(update): re-seed framework on version drift, not just in-command updates (#642 )

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

a88ff8e232

`mosaic update` only re-seeded ~/.config/mosaic when the @mosaicstack/mosaic
package was upgraded *within that same command*. When the CLI is upgraded
another way — a direct `npm i -g @mosaicstack/mosaic`, or an update run where
only sibling packages were outdated — the framework files (launchers, runtime
adapters, fleet tools) silently stayed stale, so shipped fixes never activated.
Critically, the "all packages up to date" branch returned before any re-seed
could run, so a drifted-but-current host had no path to reconcile.

Add framework drift detection: compare the on-disk schema version
(~/.config/mosaic/.framework-version) against the version bundled in the
installed package (FRAMEWORK_VERSION in the bundled install.sh). `mosaic update`
now re-seeds when the mosaic package updated OR the on-disk framework is older
than bundled — including from the up-to-date branch. Detection is conservative:
if either version can't be read it reports no drift, so a missing/unreadable
version file never triggers an unexpected re-seed. `--no-reseed` still opts out.

The re-seed + unit-refresh + relaunch sequence is factored into a single local
helper shared by both the post-update and drift paths (no behavior change to the
existing path beyond also firing on drift).

New exported, unit-tested helpers in update-checker.ts:
- readInstalledFrameworkVersion / readBundledFrameworkVersion
- checkFrameworkDrift -> { drifted, installed, bundled }

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

jason.woltje merged commit 16ae809442 into main

2026-06-24 05:04:35 +00:00

jason.woltje referenced this issue from a commit

2026-06-24 05:04:36 +00:00

fix(update): re-seed framework on version drift, not just in-command updates (#642) (#646)

jason.woltje referenced this pull request

2026-06-24 05:18:39 +00:00

chore(release): mosaic CLI 0.0.42 #648

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#646