Skip to content

v0.1.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Sep 09:22
· 4 commits to main since this release
v0.1.4
c8ac0da

Accept quasar 0.2 in the peer range

The connection contract these packages use — a default export with
connection(name?) on @c9up/quasar/services/main — is unchanged in 0.2.0,
but the range still said ^0.1.0, so every install reported an unmet peer
against the version actually on disk.

Release 0.1.4.

Keep the dev-dependency alignment, drop the workspace: protocol

The internal ranges had been rewritten to workspace:^. That resolves inside
this monorepo and nowhere else: every package CI checks out its own repository
alone and runs pnpm install, where the protocol has no workspace to point at
and fails with ERR_PNPM_WORKSPACE_PKG_NOT_FOUND before a single test runs. The
concrete ranges are back; the dev-dependency bumps that came with the same edit
are kept, and now match what the lockfile already resolved.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_014TPESFkjvtFdG6f3cSy6Zi

Changes since v0.1.3.

Assets 2
Loading