Compatibility
Auditaur has Rust crates, an npm frontend package, a CLI binary, and app-side runtime code. Keep them from the same release line when possible.
Current versions
Section titled “Current versions”| Component | Install name | Current documented version |
|---|---|---|
| CLI binary | cargo install auditaur-cli | 0.4.0 |
| Tauri plugin | tauri-plugin-auditaur | 0.4.0 |
| Frontend SDK | @auditaur/api | 0.5.1 |
| Core/collector crates | auditaur-core, auditaur-collector | 0.4.0 |
| Macro crate | tauri-plugin-auditaur-macros | 0.4.0 |
Recommended app pins
Section titled “Recommended app pins”[dependencies]tauri-plugin-auditaur = "0.4.0"tracing = "0.1"tracing-subscriber = "0.3"npm install @auditaur/api@0.5.1What should match?
Section titled “What should match?”| Pair | Why it matters |
|---|---|
| CLI and Rust plugin | They share SQLite schema expectations, discovery metadata, health checks, and drive bridge status interpretation. |
| Rust plugin and frontend SDK | They share the frontend export command, record envelopes, trace propagation carriers, and drive bridge protocol. |
| Plugin and macro crate | tauri-plugin-auditaur re-exports macros; release automation keeps the macro crate and plugin crate aligned. |
Signs of version skew
Section titled “Signs of version skew”Run:
auditaur health --jsonauditaur doctor --db "<databasePath>" --jsonVersion skew commonly appears as schema validation failures, capability warnings, frontend export failures, missing drive bridge fields, or unsupported bridge action compatibility messages.
Source checkout development
Section titled “Source checkout development”Inside the Auditaur repository, use source commands when testing local changes:
cargo run -p auditaur-cli -- doctorcargo run -p auditaur-cli -- apps --json
cd packages\apinpm run buildFor the dogfood app, build the local frontend package before starting Tauri:
cd examples\dogfoodnpm installnpm run build:apinpm run tauri devUpdating an app
Section titled “Updating an app”- Update the Rust plugin version in
src-tauri\Cargo.toml. - Update
@auditaur/apiin the frontend package manager lockfile. - Restart the Tauri dev process so a fresh session is created.
- Run
auditaur doctor tauri --path src-tauri --json. - Run
auditaur apps --jsonand confirm the active session is readable and schema-valid.