From d001a96ec25de72a793bd54a62e6c7ebbc808b3b Mon Sep 17 00:00:00 2001 From: Jarvis Date: Sun, 5 Apr 2026 09:11:56 -0500 Subject: [PATCH] fix: revert mosaic to 0.0.22 alpha + republish macp MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 macp@0.0.2 as "already published", leaving the bad copy on the registry. Installing mosaic@0.1.0 resolves macp@0.0.2 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/mosaic@0.1.0 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 --- docs/MISSION-MANIFEST.md | 2 +- docs/scratchpads/cli-unification-20260404.md | 19 ++++++++++++++++++- packages/macp/package.json | 2 +- packages/mosaic/package.json | 2 +- 4 files changed, 21 insertions(+), 4 deletions(-) diff --git a/docs/MISSION-MANIFEST.md b/docs/MISSION-MANIFEST.md index f71b48e..6c7588c 100644 --- a/docs/MISSION-MANIFEST.md +++ b/docs/MISSION-MANIFEST.md @@ -12,7 +12,7 @@ **Progress:** 8 / 8 milestones **Status:** completed **Last Updated:** 2026-04-05 -**Release:** [`mosaic-v0.1.0`](https://git.mosaicstack.dev/mosaicstack/mosaic-stack/releases/tag/mosaic-v0.1.0) (`@mosaicstack/mosaic@0.1.0`) +**Release:** [`mosaic-v0.0.22`](https://git.mosaicstack.dev/mosaicstack/mosaic-stack/releases/tag/mosaic-v0.0.22) (`@mosaicstack/mosaic@0.0.22`, alpha — stays in 0.0.x until GA) ## Success Criteria diff --git a/docs/scratchpads/cli-unification-20260404.md b/docs/scratchpads/cli-unification-20260404.md index 5ebb87b..0f4de0a 100644 --- a/docs/scratchpads/cli-unification-20260404.md +++ b/docs/scratchpads/cli-unification-20260404.md @@ -199,9 +199,26 @@ Parallel-dispatched in isolated worktrees. All merged: - Git tag: `mosaic-v0.1.0` (scoped to avoid collision with existing `v0.1.0` repo tag) — pushed to origin on merge sha. - Gitea release: https://git.mosaicstack.dev/mosaicstack/mosaic-stack/releases/tag/mosaic-v0.1.0 — "@mosaicstack/mosaic v0.1.0 — CLI Unification". +### Wave 6 — M8 correction (version regression) + +PR #419 bumped `@mosaicstack/mosaic` 0.0.21 → 0.1.0 and released as `mosaic-v0.1.0`. This was wrong on two counts: + +1. **Versioning policy violation.** The project stays in `0.0.x` alpha until GA. Minor bump to `0.1.0` jumped out of alpha without authorization. +2. **macp exports fix never reached the registry.** PR #415 fixed `packages/macp/package.json` `exports.default` pointing at `./src/index.ts`, but did NOT bump macp's version. When the post-merge publish workflow ran on #419, it published `@mosaicstack/mosaic@0.1.0` but `@mosaicstack/macp@0.0.2` was "already published" so the fix was silently skipped. Result: users running `mosaic update` got mosaic 0.1.0 which depends on macp and resolves to the still-broken registry copy of macp@0.0.2, failing with `ERR_MODULE_NOT_FOUND` on `./src/index.ts` at CLI startup. + +Correction PR: + +- `@mosaicstack/mosaic` 0.1.0 → `0.0.22` (stay in alpha) +- `@mosaicstack/macp` 0.0.2 → `0.0.3` (force republish with the exports fix) +- Delete Gitea tag `mosaic-v0.1.0` + release +- Delete `@mosaicstack/mosaic@0.1.0` from the Gitea npm registry so `latest` reverts to the highest remaining version +- Create tag `mosaic-v0.0.22` + Gitea release + +**Lesson captured:** every package whose _source_ changes must also have its _version_ bumped, because the publish workflow silently skips "already published" versions. `@mosaicstack/macp@0.0.2` had the bad exports in the registry from day one; the in-repo fix in #415 was invisible to installed-from-registry consumers until the version bumped. + ### Mission outcome -All 8 milestones, all 8 success criteria, merged to main, green CI on every PR, released. Two sessions total (~10h combined). No rollbacks, no blocked milestones, no escalations required. +All 8 milestones, all 8 success criteria met in-repo. Released as `mosaic-v0.0.22` (alpha) after correcting an incorrect 0.1.0 version bump + missed macp republish. Two sessions total (~10h combined) plus a follow-up correction PR. ## Verification Evidence diff --git a/packages/macp/package.json b/packages/macp/package.json index 6486e47..5b55126 100644 --- a/packages/macp/package.json +++ b/packages/macp/package.json @@ -1,6 +1,6 @@ { "name": "@mosaicstack/macp", - "version": "0.0.2", + "version": "0.0.3", "repository": { "type": "git", "url": "https://git.mosaicstack.dev/mosaicstack/mosaic-stack.git", diff --git a/packages/mosaic/package.json b/packages/mosaic/package.json index 78c0799..9d3b7f9 100644 --- a/packages/mosaic/package.json +++ b/packages/mosaic/package.json @@ -1,6 +1,6 @@ { "name": "@mosaicstack/mosaic", - "version": "0.1.0", + "version": "0.0.22", "repository": { "type": "git", "url": "https://git.mosaicstack.dev/mosaicstack/mosaic-stack.git",