Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow updating workflow current version after close #5860

Merged
merged 4 commits into from May 21, 2024

Conversation

yycptt
Copy link
Member

@yycptt yycptt commented May 6, 2024

What changed?

  • Allow updating workflow current version after close

Why?

  • Workflow state machine could be updated after workflow closed from user POV

How did you test it?

  • Existing tests & added new unit tests

Potential risks

Documentation

Is hotfix candidate?

@yycptt yycptt requested a review from yux0 May 6, 2024 22:55
@yycptt yycptt requested a review from a team as a code owner May 6, 2024 22:55
@yycptt yycptt merged commit 81e65a8 into temporalio:main May 21, 2024
42 checks passed
@yycptt yycptt deleted the current-version-after-close branch May 21, 2024 01:09
yycptt added a commit that referenced this pull request May 21, 2024
## What changed?
<!-- Describe what has changed in this PR -->
- Account for state only changes in LastWriteVersion
- ^ also means LastWriteVersion could change after workflow is closed.
- NOTE: this PR is stacked on top of
#5860

## Why?
<!-- Tell your future self why have you made these changes -->
- Account for state only changes

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- Existing tests & new unit tests

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
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.

None yet

2 participants