Add CONTINUE_AS_NEW_VERSIONING_BEHAVIOR_USE_RAMPING_VERSION#760
Merged
Add CONTINUE_AS_NEW_VERSIONING_BEHAVIOR_USE_RAMPING_VERSION#760
CONTINUE_AS_NEW_VERSIONING_BEHAVIOR_USE_RAMPING_VERSION#760Conversation
Sushisource
approved these changes
Apr 8, 2026
Co-authored-by: Spencer Judge <sjudge@hey.com>
ShahabT
approved these changes
Apr 8, 2026
Shivs11
approved these changes
Apr 9, 2026
…ing_behavior in versioning info and autoupgradeinfo
…behavior-use-ramping-version" This reverts commit ac2db0e.
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.
Add
CONTINUE_AS_NEW_VERSIONING_BEHAVIOR_USE_RAMPING_VERSIONTo enable the use case of Continue-as-new-upgrading a user-specified cohort of Pinned workflows before any other workflows are upgraded. To do this, user would first set Ramp percentage to zero, then tell (likely via signal) their cohort of workflows to Continue-as-new with this initial behavior, watch that bake, repeat for whatever other cohorts are desired, and finally do a percentage-based ramp which applies to new workflows as well as workflows doing
CONTINUE_AS_NEW_VERSIONING_BEHAVIOR_AUTO_UPGRADENo
Does not break the server