---
title: "2026-08-07 mono automation audit"
description: "Audited mono documentation and automation for CI, versioning, packaging, releases, builds, and deployments."
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-07 mono automation audit

## Work Done

- Audited the current `virdx/mono` main checkout, focusing on root Nx/Bun/Pixi configuration, all GitHub Actions workflows, per-project Nx targets, conda recipes, version helpers, container definitions, manual Tekton build scripts, and deployment documentation.
- Produced a concrete inventory for the coordinating agent, including current workflow patterns and high-risk inconsistencies: release documentation disagrees about manual versus Nx-driven versioning; no actual Nx release/tag workflow exists; Python package releases are manual uploads; TypeScript publishing is not automated; app version groups are not connected to deployment automation; and project target coverage is uneven.
- Identified specific defects and drift, including the docs Containerfile copying removed `apps/inference/README.md`, dashboard-api's duplicate version sources interacting incorrectly with the Pixi version action, vxdata-explorer's conda constraints excluding current 2.1 SDK/schema versions, missing test path triggers, matrix references in non-matrix workflows, stale deployment documentation, and incomplete root inventory.

## Lessons Learned: Pitfalls

- The infrastructure conda-release SOP accurately describes the existing manual package workflow, but root `AGENTS.md` presents Nx Release as the operative release mechanism. Reading either alone gives an incomplete and contradictory picture.
- `apps/docs/services/deploying_dashboard_vxdata.md` contains stale in-repo manifest paths and a misspelled build-script path, so it should not be treated as authoritative deployment state.

## Lessons Learned: Improvements

- Add one canonical automation matrix to infrastructure knowledge: project, manifest/version source, CI targets, package/image artifact, release trigger, registry, deployment trigger, and owning repo.
- Explicitly distinguish configured Nx Release groups from production release workflows, and document that configuration alone does not create tags, changelogs, packages, images, or deployments.
- Add a periodic validation for documentation/source paths used by container COPY instructions and synced-doc triggers.

Source: https://docs.virdx.dev/knowledge/inbox/2026-08-07-infrastructure-mono-automation-audit/index.mdx