Skip to content

3.3.2

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Nov 11:59
· 12 commits to main since this release
Immutable release. Only release title and notes can be modified.
3.3.2
660217d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Durable Workflow Server 3.3.2.
Git tag 3.3.2 → 660217dd1ac62701eb1fc26b08fbbaf825e777d1
Image index sha256:4aeceb423ee4c8931f00ec2936149ac6b2a75479243b3930f9c6336ccdebf912 in durableworkflow/server and ghcr.io/durable-workflow/server
Release run https://github.com/durable-workflow/server/actions/runs/42591612884

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, 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 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 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. 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 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.

Assets 3
Loading