Repository navigation
Add Deployment Options for Eager start - #645
Merged
Merged
Conversation
carlydf
approved these changes
Oct 8, 2025
stephanos
pushed a commit
that referenced
this pull request
Mar 10, 2026
**What changed?** Added `eager_worker_deployment_options` to `StartWorkflowExecutionRequest`. <!-- Tell your future self why have you made these changes --> **Why?** So server knows the versioning info of the worker who would process the eager task. Server can ignore the eager flag if the worker doesn't have the Current version. <!-- Are there any breaking changes on binary or code level? --> **Breaking changes** None <!-- If this breaks the Server, please provide the Server PR to merge right after this PR was merged. --> **Server PR**
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
Added
eager_worker_deployment_optionstoStartWorkflowExecutionRequest.Why?
So server knows the versioning info of the worker who would process the eager task. Server can ignore the eager flag if the worker doesn't have the Current version.
Breaking changes
None
Server PR