Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 54 additions & 0 deletions docs/release-notes/2.11.0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
Durable Workflow CLI 2.11.0

## Breaking: request-ID refusals have their own exit codes

When you retry `workflow:signal` or `workflow:update` with `--request-id`, the
Server can refuse the key. 2.11.0 gives those refusals their own exit codes
(cli#167, durable-workflow/.github#216):

| Refusal | 2.10.0 | 2.11.0 |
| --- | --- | --- |
| HTTP 409 `request_id_conflict`: the key already names a retained command with a different name, input or run target | exit **2** | exit **9** (`REQUEST_ID_CONFLICT`) |
| HTTP 409 `request_id_ambiguous`: the key matches more than one retained command | exit **2** | exit **10** (`REQUEST_ID_AMBIGUOUS`) |

**Scripts that treated exit 2 as "the key was refused" must also check 9 and
10.** Every other 409, such as `run_not_active`, still exits 2.

Both are definite refusals. Nothing was recorded and no receipt was selected,
so the CLI prints no "outcome unknown" warning and never resends the command.
The JSON error envelope keeps `request_id`, `reason` and the Server's
`server_response`.
- For a conflict, repeat the original command unchanged to read its receipt,
or choose a new `--request-id`.
- For an ambiguity, retrying unchanged fails the same way. A new
`request_id.ambiguous` next step explains this.

## Legacy receipts are labelled

A receipt the Server retained before it compared command intent
(`retained: true`, `intent_verified: false`) now prints
`Intent Verified: no (legacy receipt; the Server did not compare this command's
intent with it)`, so human output never presents it as a verified match. JSON
output passes both fields through unchanged.

## Unchanged

- A `--request-id` you pass is sent verbatim. Without one, each invocation
generates one `cli-<signal|update>-<32 hex>` key and puts it in the error
envelope for a manual retry. `workflow:signal` and `workflow:update` send
exactly one request.
- `batch:*` already treated any 409 `request_id*` refusal as refused and not
retryable, and it resends only with the manifest's stored key.

## Qualification and compatibility

- These behaviours were qualified against published native Server 3.13.0. That
covers committed-response loss recovery, concurrent first sends and retries,
typed conflicts, closed and continued runs, and legacy readback with all three
ambiguity shapes. They run in the
[Published command keys](https://github.com/durable-workflow/cli/actions/workflows/published-command-keys.yml)
workflow.
- `dw server:start-dev` still embeds native Server 3.12.0, and its data
directory is unchanged from 2.10.0.
- The CLI still uses the published Rust SDK 4.18.0. Building from source needs
Rust 1.99.
2 changes: 1 addition & 1 deletion rust/Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion rust/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "dw"
version = "2.10.0"
version = "2.11.0"
edition = "2021"
rust-version = "1.99"
description = "Command-line interface for Durable Workflow Server and Cloud"
Expand Down
Loading