Skip to content

build: qsv-client >= 0.4.0 - #22

Merged
jqnatividad merged 1 commit into
dathere:mainfrom
jqnatividad:qsv-client-0.4.0
Oct 15, 2026
Merged

jqnatividad merged 1 commit into
dathere:mainfrom
jqnatividad:qsv-client-0.4.0

Conversation

@jqnatividad

Copy link
Copy Markdown
Collaborator

Upgrades to qsv-client 0.4.0.

What changed upstream

  • qsv 25.0.0+ is now required, and the client runs qsv --capabilities before its first command. The Docker image already ships qsv 25.0.0 (build: qsv 25.0.0 in the image, qsv-client >= 0.3.0 #21).
  • QsvVersionError is now a QsvError subclass.
  • The --version / --list fallback is gone.

Changes here

  • pyproject.toml / uv.lock: qsv-client>=0.4.0.
  • qsv_profiling.py: drop the now-redundant QsvVersionError from _QSV_FAILURES and fix the stale comment.
  • test_qsv_profiling.py: the fake qsv answers --capabilities like qsv 25.0.0 (6 tests failed without it). The qsvlite/no-describegpt test now uses capabilities instead of the removed fallback. Added a test that a qsv older than 25.0.0 makes a pass return None instead of raising.

Note for local dev

A local qsv older than 25.0.0 now makes every profiling pass fail with QsvVersionError. Upgrade qsv before pulling this.

Testing

uv run pytest: 1024 passed, 2 skipped. ruff check is clean.

🤖 Generated with Claude Code

qsv-client 0.4.0 requires qsv 25.0.0+ (already in the image) and checks
`qsv --capabilities` before a client's first run.

- QsvVersionError is now a QsvError subclass, so drop it from
  _QSV_FAILURES and fix the comment.
- The fake qsv in the profiling tests answers --capabilities like qsv
  25.0.0; the qsvlite test no longer relies on the removed
  --version/--list fallback.
- New test: a qsv older than 25.0.0 makes a profiling pass return None
  instead of raising.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jqnatividad
jqnatividad merged commit eb86507 into dathere:main Oct 15, 2026
6 checks passed
@jqnatividad
jqnatividad deleted the qsv-client-0.4.0 branch October 15, 2026 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant