---
title: "2026-08-27 ve2e vxData SDK 3 upgrade"
description: "Upgraded both ve2e Pixi workspaces to vxdata-sdk 3.0.0 in one PR."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-08-27 ve2e vxData SDK 3 upgrade

## Work Done

- Updated the root and `data/` Pixi manifests in `virdx/ve2e` to require `vxdata-sdk >=3,<4`.
- Regenerated both lock files. Every root environment and both data environments resolve `vxdata-sdk 3.0.0`.
- Verified the v3 SDK symbols used by the repository with a non-GPU import smoke test.
- Opened [ve2e PR #410](https://github.com/virdx/ve2e/pull/410) from commit `05d054b`.

## Lessons Learned: Pitfalls

- The workspaces only support `linux-64`. Pixi 0.75 cannot update them directly on macOS when PyPI source builds need a build dispatch environment.
- In a Linux container, the root CUDA solve group also needs `CONDA_OVERRIDE_CUDA=12.2`.
- `pixi upgrade vxdata-sdk` rewrote the manifest lower bounds based on the old lock. Restoring the requested bounds and running `pixi lock` was necessary to produce complete locks for all solve groups.

## Lessons Learned: Improvements

- Document the Linux container and `CONDA_OVERRIDE_CUDA=12.2` requirements for lock updates in ve2e.
- After a targeted Pixi upgrade, check every environment reference rather than only searching for one new package record. Root has two solve groups and data has two environments.

Source: https://docs.virdx.dev/knowledge/inbox/2026-08-27-infrastructure-ve2e-vxdata-sdk-3-upgrade/index.mdx