fix: bump memory/queue/storage to 0.0.4 to force republish #423

jason.woltje · 2026-04-05T14:36:08Z

jason.woltje commented

2026-04-05 14:36:08 +00:00

Third correction wave for the same systemic publish-skip bug (after PR #421 for macp and PR #422 for brain/forge/log).

Problem

mosaic --help crashes after npm i -g @mosaicstack/mosaic@latest with:

SyntaxError: The requested module @mosaicstack/memory does not provide an export named registerMemoryCommand

Registry copies of @mosaicstack/memory@0.0.3, @mosaicstack/queue@0.0.3, and @mosaicstack/storage@0.0.3 were built and published before M5 added their registerXCommand exports. Because source changed without a version bump, the publish workflow silently skipped them.

Fix

@mosaicstack/memory 0.0.3 → 0.0.4
@mosaicstack/queue 0.0.3 → 0.0.4
@mosaicstack/storage 0.0.3 → 0.0.4
@mosaicstack/mosaic 0.0.23 → 0.0.24 (deps changed)

Verification

pnpm typecheck — all 38 tasks pass
pnpm lint — all 21 tasks pass
pnpm format:check — clean
pnpm test — memory/queue/storage/mosaic all green (mosaic: 162/162)
After merge + publish: npm i -g @mosaicstack/mosaic@latest && mosaic --help exits 0

🤖 Generated with Claude Code

Third correction wave for the same systemic publish-skip bug (after PR #421 for macp and PR #422 for brain/forge/log). ## Problem `mosaic --help` crashes after `npm i -g @mosaicstack/mosaic@latest` with: ``` SyntaxError: The requested module @mosaicstack/memory does not provide an export named registerMemoryCommand ``` Registry copies of `@mosaicstack/memory@0.0.3`, `@mosaicstack/queue@0.0.3`, and `@mosaicstack/storage@0.0.3` were built and published before M5 added their `registerXCommand` exports. Because source changed without a version bump, the publish workflow silently skipped them. ## Fix - `@mosaicstack/memory` 0.0.3 → 0.0.4 - `@mosaicstack/queue` 0.0.3 → 0.0.4 - `@mosaicstack/storage` 0.0.3 → 0.0.4 - `@mosaicstack/mosaic` 0.0.23 → 0.0.24 (deps changed) ## Verification - [x] `pnpm typecheck` — all 38 tasks pass - [x] `pnpm lint` — all 21 tasks pass - [x] `pnpm format:check` — clean - [x] `pnpm test` — memory/queue/storage/mosaic all green (mosaic: 162/162) - [ ] After merge + publish: `npm i -g @mosaicstack/mosaic@latest && mosaic --help` exits 0 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jason.woltje added 1 commit 2026-04-05 14:36:09 +00:00

chore: bump memory/queue/storage to 0.0.4 to force republish

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

f9b278a76a

Memory, queue, and storage registry copies at 0.0.3 are stale — they
were built and published before M5 added registerMemoryCommand,
registerQueueCommand, and registerStorageCommand to their src/index.ts.
Because the source changed in M5 without a version bump, the publish
workflow's "already published, skipping" tolerance silently left the
old 0.0.3 tarballs in place.

This is the same systemic bug that affected macp (fixed in PR #421) and
brain/forge/log (fixed in PR #422): whenever a package's source changes
in a PR, its version must also be bumped, or the publish workflow will
not propagate the change.

- @mosaicstack/memory   0.0.3 -> 0.0.4
- @mosaicstack/queue    0.0.3 -> 0.0.4
- @mosaicstack/storage  0.0.3 -> 0.0.4
- @mosaicstack/mosaic   0.0.23 -> 0.0.24 (deps changed)

After publish, 'npm i -g @mosaicstack/mosaic@latest && mosaic --help'
must exit 0 and print the alphabetized command list.

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

jason.woltje merged commit 417805f330 into main

2026-04-05 14:39:16 +00:00

jason.woltje deleted branch fix/bump-stale-memory-queue-storage

2026-04-05 14:39:17 +00:00

jason.woltje referenced this issue from a commit

2026-04-05 14:39:17 +00:00

fix: bump memory/queue/storage to 0.0.4 to force republish (#423)

jason.woltje referenced this issue from a commit

2026-04-05 14:50:54 +00:00

docs: finalize CLI unification mission at mosaic-v0.0.24

jason.woltje referenced this pull request

2026-04-05 14:51:02 +00:00