Skip to content

Add revision_number to DeclinedTargetVersionUpgrade#762

Merged
Shivs11 merged 3 commits intomasterfrom
trampolining-rev-number
Apr 21, 2026
Merged

Add revision_number to DeclinedTargetVersionUpgrade#762
Shivs11 merged 3 commits intomasterfrom
trampolining-rev-number

Conversation

@Shivs11
Copy link
Copy Markdown
Member

@Shivs11 Shivs11 commented Apr 9, 2026

  • Added revision_number to DeclinedTargetVersionUpgrade, which already took in a deployment version.
  • Recap about what DeclinedTargetVersionUpgrade does: the main intention of this field was to "remember" which target version we have rejected when a pinned workflow declines to AU when CAN'ing. However, you could have matching partitions send you back stale target deployment versions, and we don't want to "bounce back" and CAN our pinned workflows when they see such a stale version. For that very purpose, we resort to now store the revision number here.
  • I explained it above
  • None, changes are additive.
  • Also, no changes required from the SDK perspective

temporalio/temporal#9895

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Shivs11 Shivs11 marked this pull request as ready for review April 10, 2026 00:51
@Shivs11 Shivs11 requested review from a team April 10, 2026 00:51
@Shivs11 Shivs11 enabled auto-merge (squash) April 21, 2026 20:37
@Shivs11 Shivs11 merged commit 1515646 into master Apr 21, 2026
4 checks passed
@Shivs11 Shivs11 deleted the trampolining-rev-number branch April 21, 2026 20:39
spkane31 pushed a commit that referenced this pull request Apr 24, 2026
<!-- Describe what has changed in this PR -->
- Added `revision_number` to `DeclinedTargetVersionUpgrade`, which
already took in a deployment version.
- Recap about what `DeclinedTargetVersionUpgrade` does: the main
intention of this field was to "remember" which target version we have
rejected when a pinned workflow declines to AU when CAN'ing. However,
you could have matching partitions send you back stale target deployment
versions, and we don't want to "bounce back" and CAN our pinned
workflows when they see such a stale version. For that very purpose, we
resort to now store the revision number here.


<!-- Tell your future self why have you made these changes -->
- I explained it above


<!-- Are there any breaking changes on binary or code level? -->
- None, changes are additive.
- Also, no changes required from the SDK perspective


<!-- If this breaks the Server, please provide the Server PR to merge
right after this PR was merged. -->
temporalio/temporal#9895

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

3 participants