Warn on an untested cv4pve-cli version at startup #14

Closed
opened 2026-11-02 22:55:42 +01:00 by Duckboot · 0 comments
Owner

Why

The TUI depends on cv4pve-cli output formats that are not a stable API:

  • the text format of config list
  • prune-backups arriving as a JSON string
  • the ip-addresses JSON string for CTs
  • the exit codes with --wait

All of this was verified against 2.4.0. After an upgrade, things may break in confusing ways.

Proposal

  • At startup, run cv4pve-cli --version.
  • If the version differs from the tested one, show a warning notification such as "tested with 2.4.0, found X".
  • Keep the tested version in one constant, next to a note in the README.

Done when

  • The warning shows for another version and stays silent for 2.4.0.
  • Tests are written first.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

## Why The TUI depends on `cv4pve-cli` output formats that are not a stable API: - the text format of `config list` - `prune-backups` arriving as a JSON string - the `ip-addresses` JSON string for CTs - the exit codes with `--wait` All of this was verified against 2.4.0. After an upgrade, things may break in confusing ways. ## Proposal - At startup, run `cv4pve-cli --version`. - If the version differs from the tested one, show a warning notification such as "tested with 2.4.0, found X". - Keep the tested version in one constant, next to a note in the README. ## Done when - The warning shows for another version and stays silent for 2.4.0. - Tests are written first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Duckboot added the
priority
3-low
label 2026-11-02 22:55:42 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Duckboot/cv4pve-cli-tui#14