fix: bump stale sub-package versions (brain/forge/log) #422

2026-04-05T14:23:14Z

jason.woltje commented

2026-04-05 14:23:14 +00:00

Same class of bug as the macp fix in PR #421. After M5 added registerBrainCommand / registerForgeCommand / registerLogCommand to their respective packages, the publish workflow silently skipped republishing because versions stayed at 0.0.2 (already on registry). mosaic then pulls the pre-M5 registry copies and crashes with:

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

Changes

@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 is NOT in this set because mosaic defines registerAuthCommand locally in packages/mosaic/src/commands/auth.ts rather than importing from the auth package.

memory, queue, storage, macp already had their versions bumped in their M5 PRs (or in PR #421 for macp) and are already current on the registry.

Verified

typecheck 38/38 green
lint 21/21 green
format:check clean
test: 162/162 pass in @mosaicstack/mosaic
local rebuild of brain/forge/log dist/index.js confirmed to contain the registerXCommand exports

Same class of bug as the macp fix in PR #421. After M5 added registerBrainCommand / registerForgeCommand / registerLogCommand to their respective packages, the publish workflow silently skipped republishing because versions stayed at 0.0.2 (already on registry). mosaic then pulls the pre-M5 registry copies and crashes with: ``` SyntaxError: Named export registerBrainCommand not found. The requested module @mosaicstack/brain is a CommonJS module... ``` ## Changes - @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 is NOT in this set because mosaic defines registerAuthCommand locally in packages/mosaic/src/commands/auth.ts rather than importing from the auth package. memory, queue, storage, macp already had their versions bumped in their M5 PRs (or in PR #421 for macp) and are already current on the registry. ## Verified - typecheck 38/38 green - lint 21/21 green - format:check clean - test: 162/162 pass in @mosaicstack/mosaic - local rebuild of brain/forge/log dist/index.js confirmed to contain the registerXCommand exports

jason.woltje added 1 commit 2026-04-05 14:23:15 +00:00

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

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

983951294c

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 [email protected] 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 [email protected] 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/[email protected] 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 <[email protected]>