fix: revert mosaic to 0.0.22 alpha + republish macp #421

2026-04-05T14:12:26Z

jason.woltje commented

2026-04-05 14:12:26 +00:00

Problem

Two errors shipped in PR #419 (mosaic-v0.1.0 release):

Version policy violation. @mosaicstack/mosaic was bumped 0.0.21 → 0.1.0, jumping out of 0.0.x alpha without authorization. The project stays in 0.0.x until GA.
macp exports fix never reached the registry. PR #415 fixed packages/macp/package.json exports.default (was pointing at ./src/index.ts, broke installed consumers with ERR_MODULE_NOT_FOUND), but did not bump macp version. The post-merge publish workflow silently skipped [email protected] as already published. Installing [email protected] then pulls the still-broken [email protected] from the registry and crashes on startup.

Fix

@mosaicstack/mosaic 0.1.0 → 0.0.22 (stay in alpha)
@mosaicstack/macp 0.0.2 → 0.0.3 (force republish with exports fix)
Scratchpad + manifest updated to reflect the correction and capture the lesson (version bumps required whenever source changes, or publish silently skips).

Follow-up cleanup after merge

Delete git tag mosaic-v0.1.0 + Gitea release
Delete @mosaicstack/[email protected] from Gitea npm registry
Create tag mosaic-v0.0.22 + Gitea release

## Problem Two errors shipped in PR #419 (mosaic-v0.1.0 release): 1. **Version policy violation.** @mosaicstack/mosaic was bumped 0.0.21 → 0.1.0, jumping out of 0.0.x alpha without authorization. The project stays in 0.0.x until GA. 2. **macp exports fix never reached the registry.** PR #415 fixed packages/macp/package.json exports.default (was pointing at ./src/index.ts, broke installed consumers with ERR_MODULE_NOT_FOUND), but did not bump macp version. The post-merge publish workflow silently skipped [email protected] as already published. Installing [email protected] then pulls the still-broken [email protected] from the registry and crashes on startup. ## Fix - @mosaicstack/mosaic 0.1.0 → **0.0.22** (stay in alpha) - @mosaicstack/macp 0.0.2 → **0.0.3** (force republish with exports fix) - Scratchpad + manifest updated to reflect the correction and capture the lesson (version bumps required whenever source changes, or publish silently skips). ## Follow-up cleanup after merge - Delete git tag mosaic-v0.1.0 + Gitea release - Delete @mosaicstack/[email protected] from Gitea npm registry - Create tag mosaic-v0.0.22 + Gitea release

jason.woltje added 1 commit 2026-04-05 14:12:27 +00:00

fix: revert mosaic to 0.0.22 alpha + republish macp

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

d001a96ec2

Two errors shipped in #419 (mosaic-v0.1.0 release):

1. Version policy violation — @mosaicstack/mosaic was bumped 0.0.21 →
   0.1.0, jumping out of 0.0.x alpha without authorization. The project
   stays in 0.0.x until GA. Revert to 0.0.22.

2. @mosaicstack/macp exports fix never reached the registry. PR #415
   fixed packages/macp/package.json exports.default (was pointing at
   ./src/index.ts, broke installed consumers with ERR_MODULE_NOT_FOUND),
   but did not bump macp's version. The post-merge publish workflow
   silently skipped [email protected] as "already published", leaving the bad
   copy on the registry. Installing [email protected] resolves [email protected]
   from the registry and crashes on startup. Bump macp 0.0.2 → 0.0.3 to
   force republish with the correct exports map.

Follow-up cleanup after merge:
- delete git tag mosaic-v0.1.0 + Gitea release
- delete @mosaicstack/[email protected] from Gitea npm registry so `latest`
  reverts to the highest remaining version
- create new tag mosaic-v0.0.22 + Gitea release

Co-Authored-By: Claude Opus 4.6 <[email protected]>