Jarvis 983951294c fix: bump stale sub-package versions (brain/forge/log) to republish M5 exports ...

Same systemic bug as the macp fix in the previous commit. After M5
added `registerBrainCommand`, `registerForgeCommand`, `registerLogCommand`
to packages/brain, packages/forge, packages/log, the publish workflow
silently skipped republishing those packages because their versions
stayed at 0.0.2 (already on the registry). Result: @mosaicstack/mosaic
imports `registerBrainCommand` (etc.) from @mosaicstack/brain, but the
registry copy of brain@0.0.2 predates M5 and does not contain that
export, causing:

  SyntaxError: Named export 'registerBrainCommand' not found.
  The requested module '@mosaicstack/brain' is a CommonJS module...

Fix:

- @mosaicstack/brain 0.0.2 → 0.0.3
- @mosaicstack/forge 0.0.2 → 0.0.3
- @mosaicstack/log   0.0.2 → 0.0.3
- @mosaicstack/mosaic 0.0.22 → 0.0.23 (deps changed)

@mosaicstack/auth was NOT bumped — mosaic CLI defines `registerAuthCommand`
locally in packages/mosaic/src/commands/auth.ts rather than importing
from @mosaicstack/auth, so the stale auth@0.0.2 on the registry is not
in the critical path.

memory, queue, storage, macp were already bumped in their respective
M5 PRs and are not affected.

After merge:
- Delete old dist-tag entries for brain/forge/log@0.0.2 from Gitea npm
  registry so fresh installs resolve to 0.0.3.
- No new git tag needed — 0.0.23 subsumes 0.0.22.

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

2026-04-05 09:22:46 -05:00

1.7 KiB

Raw Blame History

View Raw