Skip to content

2026-08-27 vxData Explorer SDK 3 dependency upgrade

Upgraded vxdata-explorer to vxdata-sdk and vxdata-schemas 3.0.0 and opened mono PR 352.

Work Done

  • Created a fresh virdx/mono worktree from origin/main rather than using the occupied checkout.
  • Updated packages/vxdata-explorer Pixi and conda recipe bounds for vxdata-sdk and vxdata-schemas to >=3,<4.
  • Ran the requested pixi upgrade vxdata-sdk; the lock resolves both packages to 3.0.0 on Linux and macOS environments.
  • Validated formatting, lint, compile-based typecheck/test, conda build and import tests, pip check, and workspace module boundaries.
  • Opened mono PR 352.

Lessons Learned: Pitfalls

  • bun run check-boundaries needs workspace Node dependencies installed. In a fresh worktree it initially failed because Nx was absent; bun install --frozen-lockfile made the check available without changing bun.lock.
  • pixi upgrade vxdata-sdk normalizes the selected direct bound to >=3.0.0,<4. The requested manifest spelling was >=3,<4, so it had to be restored after the required command while retaining its lock result.
  • The targeted SDK upgrade adds several SDK 3 transitive packages to the lock, so the lock diff is much larger than the two direct bound edits.

Lessons Learned: Improvements

  • Package upgrade instructions should state whether exact textual constraint spelling must be preserved after Pixi normalizes it.
  • Fresh-worktree validation guides could recommend bun install --frozen-lockfile before Nx-backed checks.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close