mosaicstack/stack
1
0
Fork 0
Code Issues 13 Pull Requests Actions Packages Projects Releases 11 Wiki Activity
Files
a00325da0ed22fbbe6dde9ce94c8fc9664d23c0b
stack/docs/scratchpads/update-checker-package-20260404.md
Jarvis 774b76447d
Some checks failed
ci/woodpecker/pr/ci Pipeline failed
Details
ci/woodpecker/push/ci Pipeline failed
Details
fix: rename all packages from @mosaic/* to @mosaicstack/* 
- Updated all package.json name fields and dependency references
- Updated all TypeScript/JavaScript imports
- Updated .woodpecker/publish.yml filters and registry paths
- Updated tools/install.sh scope default
- Updated .npmrc registry paths (worktree + host)
- Enhanced update-checker.ts with checkForAllUpdates() multi-package support
- Updated CLI update command to show table of all packages
- Added KNOWN_PACKAGES, formatAllPackagesTable, getInstallAllCommand
- Marked checkForUpdate() with @deprecated JSDoc

Closes #391
2026-04-04 21:43:23 -05:00

2.1 KiB
Raw Blame History

Scratchpad — updater package target fix (#382)

  • Objective: Fix mosaic update so modern installs query @mosaicstack/mosaic instead of stale @mosaicstack/cli.
  • Scope: updater logic, user-facing update/install hints, tests, package version bump(s).
  • Constraints: preserve backward compatibility for older @mosaicstack/cli installs if practical.
  • Acceptance:
    • fresh installs using @mosaicstack/mosaic report latest correctly
    • older installs do not regress unnecessarily
    • tests cover package lookup behavior
    • release version bumped for changed package(s)

Decisions

  • Prefer @mosaicstack/mosaic when both modern and legacy packages are installed globally.
  • For legacy @mosaicstack/cli installs, query @mosaicstack/cli first, then fall back to @mosaicstack/mosaic if the legacy package is not published.
  • Share install-target selection from packages/mosaic so both the consolidated CLI and the legacy packages/cli entrypoint print/install the same package target.
  • Extend the update cache to persist the resolved target package as well as the version so cached checks preserve the migration target.

Validation

  • pnpm install
  • pnpm --filter @mosaicstack/mosaic test -- __tests__/update-checker.test.ts
  • pnpm exec eslint --no-warn-ignored packages/mosaic/src/runtime/update-checker.ts packages/mosaic/src/cli.ts packages/mosaic/src/index.ts packages/mosaic/__tests__/update-checker.test.ts packages/cli/src/cli.ts
  • pnpm --filter @mosaicstack/mosaic lint
  • pre-push hooks: typecheck, lint, format:check

Review

  • Manual review of the updater diff caught and fixed a cache regression where fallback results would lose the resolved package target on subsequent cached checks.

Risks / Notes

  • Direct pnpm --filter @mosaicstack/mosaic typecheck and pnpm --filter @mosaicstack/cli ... checks were not representative in this worktree because packages/cli is excluded from pnpm-workspace.yaml and the standalone package check lacked the built workspace dependency graph.
  • The repo's pre-push hooks provided the authoritative validation path here and passed: root typecheck, lint, and format:check.
Reference in New Issue View Git Blame Copy Permalink