New release: alphatheta-connect@0.19.2 available (pinned: 0.15.0)

[github-actions]

A new version of alphatheta-connect is available on npm.

Current	Available
0.15.0	0.19.2

Next steps:

1. Check the changelog for breaking changes
2. Run contract tests locally: cd bridge && npm install alphatheta-connect@0.19.2 --save-exact && npx vitest run 'contracts'
3. If tests pass, update package.json and open a PR

[thewrz]

Status: blocked — not bumping. Pin stays at 0.15.0.

Investigated the bump to 0.19.2 (also checked 0.18.0 and 0.19.1). All three are unusable as published.

Broken publish — leaked file: deps

0.18.0, 0.19.1, and 0.19.2 all declare local monorepo paths in dependencies:

"metadata-connect": "file:../metadata-connect",
"onelibrary-connect": "file:../onelibrary-connect"

Those paths don't exist in the published tarball, so npm install alphatheta-connect@0.19.2 silently omits them. The bundled lib/index.js (webpack output) requires onelibrary-connect as an external CommonJS module, so any import throws:

Error: Cannot find module 'onelibrary-connect'
Require stack:
- node_modules/alphatheta-connect/lib/index.js

Our contract test (bridge/src/__tests__/contracts/alphatheta-connect-contract.test.ts) fails at import for this reason.

Compatibility is otherwise fine

Workaround-verified: metadata-connect@1.1.10 and onelibrary-connect@1.1.1 are published on npm (same maintainer). Installing them as explicit deps satisfies Node resolution, after which the contract test passes 3/3 — CDJStatus.PlayState and DeviceType enum values are unchanged from 0.15.0. So PioneerProlinkPlugin needs no code changes; only the packaging blocks the upgrade.

Upstream fix needed (notify chrisle/alphatheta-connect)

1. Replace the file:../metadata-connect / file:../onelibrary-connect specs with published npm version ranges — both libs are already on npm (metadata-connect@1.1.10, onelibrary-connect@1.1.1) — or add them to bundledDependencies / bundle them into the webpack output the way other deps are bundled.
2. Publish a patch release.
3. Clean-room verify before publishing: npm pack, install the resulting tarball in an empty directory, and require() it.

Re-evaluate once a fixed release ships. Pinned at 0.15.0 until then.