Skip to content

build: qsv 25.0.0 in the image, qsv-client >= 0.3.0 - #21

Merged
jqnatividad merged 1 commit into
dathere:mainfrom
jqnatividad:qsv-25.0.0
Oct 14, 2026
Merged

jqnatividad merged 1 commit into
dathere:mainfrom
jqnatividad:qsv-25.0.0

Conversation

@jqnatividad

Copy link
Copy Markdown
Collaborator
  • Dockerfile: QSV_VERSION 24.0.0 → 25.0.0. qsv 25.0.0 is the first release with structured JSON errors (QSV_ERROR_FORMAT=json, feat: QSV_ERROR_FORMAT=json and --capabilities for subprocess callers qsv#4765) and --capabilities, which qsv-client reads for typed errors and the version check (Run every qsv call through qsv-client #19). On 24.0.0 both fell back to plain text. The amd64 (musl) and arm64 (gnu) 25.0.0 zips both contain the full qsv binary the image extracts.
  • qsv-client >=0.1.0 → >=0.3.0; uv.lock 0.1.0 → 0.3.0. 0.2.0 bounds a timeout even when a process qsv started holds the pipes open. 0.3.0 resolves a relative stdout_path against cwd=, which doesn't affect us: AsyncQsv is built without cwd=.

Testing

  • tests/unit: 982 passed, 2 skipped, with qsv-client 0.3.0.
  • The Docker image was not built locally (no Docker daemon available).

🤖 Generated with Claude Code

qsv 25.0.0 is the first release with structured JSON errors
(QSV_ERROR_FORMAT=json, dathere/qsv#4765) and --capabilities, which
qsv-client reads for typed errors and the version check; on 24.0.0 both
fell back to plain text.

uv.lock had qsv-client 0.1.0. 0.2.0 bounds a timeout even when a process
qsv started holds the pipes open; 0.3.0 resolves a relative stdout_path
against cwd=, which doesn't affect us (AsyncQsv is built without cwd=).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jqnatividad
jqnatividad merged commit 7665d6c into dathere:main Oct 14, 2026
6 checks passed
@jqnatividad
jqnatividad deleted the qsv-25.0.0 branch October 14, 2026 23:58
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