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/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/[email protected]` | `client-pglite.*` (added in fc7fa119 without a version bump) |
| `@mosaic/[email protected]` | `factory.*`, `types.*` |
| `@mosaic/[email protected]` | `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
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/[email protected] 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/[email protected] is missing factory.* / types.* on registry
- @mosaic/[email protected] 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) <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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:
Root cause audit
Compared the file lists inside registry tarballs vs local
dist/:@mosaic/[email protected]client-pglite.*(added infc7fa119without a version bump)@mosaic/[email protected]factory.*,types.*@mosaic/[email protected]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.2in sub-1.0 semver only matches0.0.2exactly — gateway must republish with^0.0.3deps)Test plan
pnpm typecheckpassespnpm lintpassespnpm format:checkpassesmosaic gateway install+ start boots past the createPgliteDb import and the gateway becomes healthy