Skip to content

Show legacy and unknown workflow version usage - #158

Draft
rmcdaniel wants to merge 2 commits into
mainfrom
cli/220-version-usage
Draft

rmcdaniel wants to merge 2 commits into
mainfrom
cli/220-version-usage

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Open runs can still depend on a version branch that an operator intends to remove. This draft adds dw workflow:version-usage <workflow-type> <change-id> --min-version=N, with namespace validation, all-state counts, a bounded page of runs, explicit unknown reasons, help and JSON/JSONL output.

It uses the producer's corrected relative GET /workflow-version-usage route and requires literal capabilities.workflow_version_usage=true. Counts survive empty filtered pages. Invalid or inconsistent responses, missing capability, auth/storage failures, redirects and lost replies remain failures. The command sends one usage GET and does not follow its cursor automatically.

Validation: 11 focused real-CLI/loopback transport tests pass under Rust 1.86, including query encoding and namespace scope, signed integer bounds, no-request invalid arguments, unknowns, response integrity, unsupported capability, HTTP failure, redirect refusal, single-attempt behavior and offline help. All 25 parity-harness controls pass. The initial draft's completion comparison finding is corrected by retaining the existing final completion entry and its newline behavior. Normal current-head CI remains required.

The producer route is not yet published. Actual native Server acceptance remains the final integration gate before this leaves draft; no release or shared #220 closure is claimed. The operator's self-contained native dev Server requirement is now the immediate CLI priority in #160. The unrelated #157 review/activation hold remains in force.

Refs durable-workflow/.github#220, durable-workflow/workflow#1146, durable-workflow/server#1221.

@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
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