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>
43 lines
971 B
JSON
43 lines
971 B
JSON
{
|
|
"name": "@mosaicstack/memory",
|
|
"version": "0.0.4",
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://git.mosaicstack.dev/mosaicstack/mosaic-stack.git",
|
|
"directory": "packages/memory"
|
|
},
|
|
"type": "module",
|
|
"main": "dist/index.js",
|
|
"types": "dist/index.d.ts",
|
|
"exports": {
|
|
".": {
|
|
"types": "./dist/index.d.ts",
|
|
"default": "./dist/index.js"
|
|
}
|
|
},
|
|
"scripts": {
|
|
"build": "tsc",
|
|
"lint": "eslint src",
|
|
"typecheck": "tsc --noEmit",
|
|
"test": "vitest run --passWithNoTests"
|
|
},
|
|
"dependencies": {
|
|
"@mosaicstack/db": "workspace:*",
|
|
"@mosaicstack/storage": "workspace:*",
|
|
"@mosaicstack/types": "workspace:*",
|
|
"commander": "^13.0.0",
|
|
"drizzle-orm": "^0.45.1"
|
|
},
|
|
"devDependencies": {
|
|
"typescript": "^5.8.0",
|
|
"vitest": "^2.0.0"
|
|
},
|
|
"publishConfig": {
|
|
"registry": "https://git.mosaicstack.dev/api/packages/mosaicstack/npm/",
|
|
"access": "public"
|
|
},
|
|
"files": [
|
|
"dist"
|
|
]
|
|
}
|