Skip to content

Recover main after the stopped 3.0.3 release: revert #989, Compose default back to 3.0.2 #990

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rmcdaniel merged 2 commits into from
Nov 3, 2026
Merged

Recover main after the stopped 3.0.3 release: revert #989, Compose default back to 3.0.2 #990

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c287643
Revert "Merge pull request #989 from durable-workflow/docs/987-takeov…
rmcdaniel Nov 3, 2026
0821fa2
Published Compose: default to the published 3.0.2 again
rmcdaniel Nov 3, 2026
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
2 changes: 1 addition & 1 deletion docker-compose.published.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.0.3}
x-server-image: &server-image ${DW_SERVER_IMAGE:-durableworkflow/server:3.0.2}

services:
server:
Expand Down
14 changes: 5 additions & 9 deletions docs/rust-server-storage-audit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,8 @@
# Rust Server storage and upgrade audit

This is a source-audit checkpoint for [#325](https://github.com/durable-workflow/server/issues/325),
not a migration procedure, and it predates the takeover. Native 3.0.x
implements `upgrade-takeover`; its procedure, qualified scope and remaining
gaps are in the [takeover runbook](rust-server-upgrade-takeover.md). The text
below is the original audit. The PHP ownership fence is implemented in source by
not a qualified migration procedure. Rust takeover and stored-value conversion
remain unimplemented. The PHP ownership fence is implemented in source by
[#331](https://github.com/durable-workflow/server/pull/331); the frozen published
reference still lacks that fence. The reference is published Server `2.5.13`, source
`f061d64277f09b11dd9a0844b958bfab6c8e998e`, with Workflow `2.5.4`, source
Expand Down Expand Up @@ -98,9 +96,7 @@ and takeover flag stays false.
There is no mixed PHP/Rust fleet or PHP rollback after upgrade. Restoring a
pre-upgrade backup is a separate recovery action with its own data boundary.

These gates were written before the takeover existed. The
[takeover runbook](rust-server-upgrade-takeover.md#status-and-scope) records
which are now qualified and which remain open. Its design section describes
how the takeover command proves the backup, excludes other writers and resumes
after interruption. HTTP export/import remains a supported deployment
All gates above remain open. The [takeover design](rust-server-upgrade-takeover.md)
proposes how the takeover command proves the backup, excludes other writers and
resumes after interruption. HTTP export/import remains a supported deployment
transfer surface, but it does not substitute for in-place upgrade qualification.
Loading
Loading