Skip to content

Add upgrade-on-CAN support and expose CAN suggestion reasons#627

Merged
THardy98 merged 2 commits intomainfrom
pr/upgrade-on-can
Mar 20, 2026
Merged

Add upgrade-on-CAN support and expose CAN suggestion reasons#627
THardy98 merged 2 commits intomainfrom
pr/upgrade-on-can

Conversation

@THardy98
Copy link
Copy Markdown
Contributor

@THardy98 THardy98 commented Mar 18, 2026

Summary

  • Allow PINNED workflows to detect when the target worker deployment version has changed via Workflow.TargetWorkerDeploymentVersionChanged
  • Add InitialVersioningBehavior option on ContinueAsNewOptions to support upgrading to the latest version on continue-as-new (AUTO_UPGRADE)
  • Expose SuggestContinueAsNewReason flags from the server so workflows can inspect why a CAN was suggested
  • Add integration test for the full upgrade-on-CAN flow

@THardy98 THardy98 force-pushed the pr/upgrade-on-can branch from 3a63e92 to 4a30c8c Compare March 18, 2026 17:31
- Add TargetWorkerDeploymentVersionChanged to workflow context, letting
  PINNED workflows detect when their target version changed
- Add InitialVersioningBehavior on ContinueAsNewOptions, allowing
  workflows to CAN with AutoUpgrade to move to the new version
- Add SuggestContinueAsNewReason enum and SuggestedContinueAsNewReasons
  on workflow context, exposing server-provided CAN suggestion reasons
- Add integration test for CAN version upgrade flow

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@THardy98 THardy98 force-pushed the pr/upgrade-on-can branch from 4a30c8c to 150c8be Compare March 18, 2026 19:09
Fix IDE0005 analyzer error on Windows CI.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@THardy98 THardy98 marked this pull request as ready for review March 18, 2026 22:41
@THardy98 THardy98 requested a review from a team as a code owner March 18, 2026 22:41
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