fix(packages): republish @mosaic/config and bump dependents #386

jason.woltje · 2026-04-05T01:52:20Z

jason.woltje commented

2026-04-05 01:52:20 +00:00

Summary

mosaic gateway install was failing with ERR_PACKAGE_PATH_NOT_EXPORTED because the published @mosaic/config@0.0.1 on the Gitea registry is the old tooling-configs package (tsconfig/eslint/prettier), not the runtime config loader that commit 04a80fb9 repurposed the package into. Version was never bumped, so consumers kept pulling the stale tarball.

Changes

@mosaic/config: 0.0.1 → 0.0.2 (triggers publish of runtime variant with . export)
@mosaic/gateway: 0.1.0 → 0.0.5 (republish with fixed dep; 0.1.0 was an unintended semver jump and has been deleted from the Gitea registry to restore the 0.0.x lineage)
@mosaic/mosaic: 0.0.18 → 0.0.19 (CLI ships with fixed transitive resolution)

Test plan

pnpm typecheck passes
pnpm lint passes
pnpm format:check passes
CI publish pipeline pushes new versions to Gitea registry
mosaic gateway install succeeds and gateway becomes healthy

## Summary `mosaic gateway install` was failing with `ERR_PACKAGE_PATH_NOT_EXPORTED` because the published `@mosaic/config@0.0.1` on the Gitea registry is the old tooling-configs package (tsconfig/eslint/prettier), not the runtime config loader that commit 04a80fb9 repurposed the package into. Version was never bumped, so consumers kept pulling the stale tarball. ## Changes - `@mosaic/config`: 0.0.1 → 0.0.2 (triggers publish of runtime variant with `.` export) - `@mosaic/gateway`: 0.1.0 → 0.0.5 (republish with fixed dep; 0.1.0 was an unintended semver jump and has been deleted from the Gitea registry to restore the 0.0.x lineage) - `@mosaic/mosaic`: 0.0.18 → 0.0.19 (CLI ships with fixed transitive resolution) ## Test plan - [x] `pnpm typecheck` passes - [x] `pnpm lint` passes - [x] `pnpm format:check` passes - [ ] CI publish pipeline pushes new versions to Gitea registry - [ ] `mosaic gateway install` succeeds and gateway becomes healthy

jason.woltje added 1 commit 2026-04-05 01:52:21 +00:00

fix(packages): republish @mosaic/config and bump dependents

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

116b91d2ae

The published @mosaic/config@0.0.1 on the Gitea registry is the
stale tooling-configs package (tsconfig/eslint/prettier) with only
subpath exports. When the package was repurposed in 04a80fb9 as the
runtime config loader, its version was never bumped, so consumers
that pull from the registry still get the old tarball.

This caused `mosaic gateway install` to fail with
ERR_PACKAGE_PATH_NOT_EXPORTED when gateway imported loadConfig from
@mosaic/config at runtime.

- Bump @mosaic/config to 0.0.2 so CI publishes the runtime variant
- Bump @mosaic/gateway to 0.0.5 to republish with the fixed dep
  (0.1.0 was an unintended semver jump; deleted from registry to
  restore 0.0.x lineage)
- Bump @mosaic/mosaic to 0.0.19 so the CLI ships with the fixed
  transitive dep resolution

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

jason.woltje merged commit 255ba46a4d into main

2026-04-05 01:56:58 +00:00

jason.woltje referenced this issue from a commit

2026-04-05 01:56:58 +00:00

fix(packages): republish @mosaic/config and bump dependents (#386)

jason.woltje referenced this issue from a commit

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

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

jason.woltje referenced this pull request

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

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

Sign in to join this conversation.