Skip to content

Ship Workflow compatibility fix in Server 2.5.6 - #308

Merged
rmcdaniel merged 2 commits into
mainfrom
fix/workflow-636-compatibility
Oct 7, 2026
Merged

rmcdaniel merged 2 commits into
mainfrom
fix/workflow-636-compatibility

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Oct 6, 2026 •

Copy link
Copy Markdown
Member

Server 2.5.6

Rebuild the pinned Server consumer with published Workflow 2.4.6 for durable-workflow/workflow#636.

The fix keeps an explicitly supplied run authoritative when its compatibility marker is null. It avoids an unnecessary relationship lookup and the resulting Laravel lazy-loading violation. Task-marker precedence and the omitted-run fallback are preserved.

  • Update the exact Workflow requirement and resolved package.
  • Advance Server to 2.5.6 and Helm to 0.1.143 through the existing source release manifest.
  • Synchronize the existing Compose, Kubernetes and Helm defaults.

No schema or portable worker protocol change is involved. Qualify the source, publish both architectures, verify the embedded package identity and run the exact published PHP/Python/Rust lifecycle matrix before calling the Server consumer delivered. Cloud deployment qualification remains separate.

The initial source run passed 2,546 of 2,547 cases. The remaining failure read a calendar-minute rejection counter after requests made on the live clock. This PR freezes time for that existing quota test, preserving its exact assertions and production counter behavior. The normal checks rerun on the corrected head.

@rmcdaniel
rmcdaniel merged commit 1588ed9 into main Oct 7, 2026
15 checks passed
@rmcdaniel
rmcdaniel deleted the fix/workflow-636-compatibility branch October 7, 2026 00:16
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.

2 participants