VersionStatus for WorkerDeploymentVersions#595
Merged
Conversation
ShahabT
approved these changes
May 25, 2025
ShahabT
reviewed
May 26, 2025
cretz
reviewed
May 27, 2025
Contributor
cretz
left a comment
cretz
left a comment
There was a problem hiding this comment.
(deferring to @Sushisource who has more background here than I do, nothing syntactically wrong from my POV)
Sushisource
approved these changes
May 27, 2025
Member
Sushisource
left a comment
Sushisource
left a comment
There was a problem hiding this comment.
LGTM including comment on other PR about docstrings in the list msg
stephanos
pushed a commit
that referenced
this pull request
Mar 10, 2026
_**READ BEFORE MERGING:** All PRs require approval by both Server AND SDK teams before merging! This is why the number of required approvals is "2" and not "1"--two reviewers from the same team is NOT sufficient. If your PR is not approved by someone in BOTH teams, it may be summarily reverted._ <!-- Describe what has changed in this PR --> **What changed?** - add VersionStatus inside `WorkerDeploymentVersionInfo` + `WorkerDeploymentVersionSummary` <!-- Tell your future self why have you made these changes --> **Why?** - right now, the UI code deduces the status of a version by checking `CurrentSince`, `RampingSince` and other attributes. This can just be simplified by adding this enum and the server doing the heavy lifting instead. <!-- 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** - [741011](temporalio/temporal#7804)
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
4 participants
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.
READ BEFORE MERGING: All PRs require approval by both Server AND SDK teams before merging! This is why the number of required approvals is "2" and not "1"--two reviewers from the same team is NOT sufficient. If your PR is not approved by someone in BOTH teams, it may be summarily reverted.
What changed?
WorkerDeploymentVersionInfo+WorkerDeploymentVersionSummaryWhy?
CurrentSince,RampingSinceand other attributes. This can just be simplified by adding this enum and the server doing the heavy lifting instead.Breaking changes
Server PR