From b608e1bcab47b9deb3bf198d73f73379f32c76c7 Mon Sep 17 00:00:00 2001 From: Richard McDaniel <1130888+rmcdaniel@users.noreply.github.com> Date: Mon, 9 Nov 2026 07:47:16 +0000 Subject: [PATCH] Prepare Native Server 3.3.2 release notes and Compose default Describe the qualified local-record batching and coherent workflow description changes without claiming benchmark speedups. Preserve schema, protocol, capability, SDK and rollback contracts and list the remaining deferred work. Publication and exact artifact qualification follow the release-source train. Refs #325, #1068 and #1075. Co-Authored-By: Codex --- docker-compose.published.yml | 2 +- docs/releases/3.3.2.md | 47 ++++++++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+), 1 deletion(-) create mode 100644 docs/releases/3.3.2.md diff --git a/docker-compose.published.yml b/docker-compose.published.yml index 83605822c..0c8cbde37 100644 --- a/docker-compose.published.yml +++ b/docker-compose.published.yml @@ -16,7 +16,7 @@ name: durable-workflow-server # release whose default names another image). Set DW_SERVER_IMAGE to run # any other native image, by tag or digest; pin a digest for production # change control. -x-server-image: &server-image ${DW_SERVER_IMAGE:-durableworkflow/server:3.3.1} +x-server-image: &server-image ${DW_SERVER_IMAGE:-durableworkflow/server:3.3.2} services: server: diff --git a/docs/releases/3.3.2.md b/docs/releases/3.3.2.md new file mode 100644 index 000000000..4942dacbf --- /dev/null +++ b/docs/releases/3.3.2.md @@ -0,0 +1,47 @@ +# Durable Workflow Server 3.3.2 (native) + +Server 3.3.2 is a patch release of the native (Rust) Server, published as +`durableworkflow/server:3.3.2` and `ghcr.io/durable-workflow/server:3.3.2`. +The published Compose file defaults to it. Rolling tags move separately after +qualification. + +## Upgrade + +There is no schema upgrade from 3.3.1 or 3.3.0. MySQL, MariaDB and PostgreSQL +remain at native schema 11; SQLite remains at schema 10. The worker protocol +stays at `1.20`, the control plane at version `2`, and capabilities are unchanged. +Existing clients need no SDK release for these internal changes. + +For upgrades from 3.2.x or earlier, follow the +[3.3.0 upgrade and rollback instructions](3.3.0.md#upgrade), including backup, +explicit `schema-upgrade` and condition-wait rollback constraints. This patch +does not relax those constraints or repair a mixed condition-wait chain. + +## Changes + +- [PR #1110](https://github.com/durable-workflow/server/pull/1110) batches local + activity execution, attempt and history records in command order inside the + existing completion transaction. Payload and history budgets are checked + before buffered writes; failure still rolls back the completion. History + sequence allocation and canonical stored records retain their existing + ordering and authority. Batches flush before other commands or reads that + need the buffered records. +- [PR #1112](https://github.com/durable-workflow/server/pull/1112) reads a workflow + description through one consistent read-only snapshot and one connection. + Run state, command journal, memo, routing, search attributes, updates and + failure/projection details share that snapshot. This also applies to MySQL + and MariaDB sessions configured READ COMMITTED. The native start payload is + reused where its routing authority is identical; legacy projection metadata + keeps its own first-event authority. + +The paired poll-cache writer remains deferred under +[issue #1063](https://github.com/durable-workflow/server/issues/1063). Other +performance-report items remain tracked separately, including continuation +support. No benchmark speedup or latency improvement is claimed. + +## Known limitations + +The [3.3.0 known limitations](3.3.0.md#known-limitations) still apply. +Backend query-count, budget and concurrent-transition controls establish source +behavior; exact published-image compatibility is qualified separately. Neither +result reproduces the reporter's benchmark.