fix(packages): bump db/memory/queue for PGlite + adapter factories #389

jason.woltje · 2026-04-05T02:16:30Z

jason.woltje commented

2026-04-05 02:16:30 +00:00

Summary

Same class of bug as #386: source content changed without a version bump, so the published tarballs on Gitea are stale and missing exports that the gateway imports at runtime.

Next failure the user hit after #386 landed:

SyntaxError: The requested module '@mosaic/db' does not provide an export named 'createPgliteDb'

Root cause audit

Compared the file lists inside registry tarballs vs local dist/:

Package	Registry missing
`@mosaic/db@0.0.2`	`client-pglite.*` (added in `fc7fa119` without a version bump)
`@mosaic/memory@0.0.2`	`factory.`, `types.`
`@mosaic/queue@0.0.2`	`factory.`, `types.`

Changes

@mosaic/db: 0.0.2 → 0.0.3
@mosaic/memory: 0.0.2 → 0.0.3
@mosaic/queue: 0.0.2 → 0.0.3
@mosaic/gateway: 0.0.5 → 0.0.6 (required because ^0.0.2 in sub-1.0 semver only matches 0.0.2 exactly — gateway must republish with ^0.0.3 deps)

Test plan

pnpm typecheck passes
pnpm lint passes
pnpm format:check passes
CI publish pipeline pushes new tarballs
mosaic gateway install + start boots past the createPgliteDb import and the gateway becomes healthy

## Summary Same class of bug as #386: source content changed without a version bump, so the published tarballs on Gitea are stale and missing exports that the gateway imports at runtime. Next failure the user hit after #386 landed: ``` SyntaxError: The requested module '@mosaic/db' does not provide an export named 'createPgliteDb' ``` ## Root cause audit Compared the file lists inside registry tarballs vs local `dist/`: | Package | Registry missing | |---|---| | `@mosaic/db@0.0.2` | `client-pglite.*` (added in fc7fa119 without a version bump) | | `@mosaic/memory@0.0.2` | `factory.*`, `types.*` | | `@mosaic/queue@0.0.2` | `factory.*`, `types.*` | ## Changes - `@mosaic/db`: 0.0.2 → 0.0.3 - `@mosaic/memory`: 0.0.2 → 0.0.3 - `@mosaic/queue`: 0.0.2 → 0.0.3 - `@mosaic/gateway`: 0.0.5 → 0.0.6 (required because `^0.0.2` in sub-1.0 semver only matches `0.0.2` exactly — gateway must republish with `^0.0.3` deps) ## Test plan - [x] `pnpm typecheck` passes - [x] `pnpm lint` passes - [x] `pnpm format:check` passes - [ ] CI publish pipeline pushes new tarballs - [ ] `mosaic gateway install` + start boots past the createPgliteDb import and the gateway becomes healthy

jason.woltje added 1 commit 2026-04-05 02:16:31 +00:00

fix(packages): bump db/memory/queue for PGlite + adapter factories

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

bf9bcba1ac

Same class of bug as #386: source content changed without a version
bump, so the published tarballs on Gitea are stale and missing exports
that the gateway imports at runtime.

- @mosaic/db@0.0.2 registry tarball has no client-pglite.* files —
  gateway crashes with "does not provide an export named createPgliteDb"
  (createPgliteDb was added in fc7fa119 without bumping the version)
- @mosaic/memory@0.0.2 is missing factory.* / types.* on registry
- @mosaic/queue@0.0.2 is missing factory.* / types.* on registry

Bumps:
- @mosaic/db 0.0.2 → 0.0.3
- @mosaic/memory 0.0.2 → 0.0.3
- @mosaic/queue 0.0.2 → 0.0.3
- @mosaic/gateway 0.0.5 → 0.0.6 (required because ^0.0.2 in sub-1.0
  semver only matches 0.0.2 exactly, so gateway must republish with
  ^0.0.3 deps)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

jason.woltje merged commit 80994bdc8e into main

2026-04-05 02:20:24 +00:00

jason.woltje referenced this issue from a commit

2026-04-05 02:20:26 +00:00

fix(packages): bump db/memory/queue for PGlite + adapter factories (#389)

jason.woltje referenced this pull request

2026-04-05 03:09:21 +00:00

fix(mosaic): resumable gateway install + prominent admin token #393

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#389