Skip to content

Conversation

@yycptt
Copy link
Member

@yycptt yycptt commented Jan 21, 2026

What changed?

  • Always marshal migration execution info using businessID to be compatible with the logic in cloud.
  • Unmarshaling part still accepts both workflowID and businessID so that people can upgrade from OSS v1.30.
  • Depends on Fix migration workflow breaking change for OSS #9085
  • This change will be part of OSS v1.31 but not v1.30.

Why?

  • Fix breaking changes for cloud

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

@yycptt yycptt requested a review from yux0 January 21, 2026 20:37
@yycptt yycptt requested review from a team as code owners January 21, 2026 20:37
@yycptt yycptt changed the title Fix migration workflow break change in cloud Fix migration workflow break change for cloud Jan 21, 2026
yycptt added a commit that referenced this pull request Jan 26, 2026
## What changed?
- Use plain go struct inside migration workflow activity input output
- Customize the json encoding/decoding for migration execution info and
make it backward & forward compatible.
- This will temporary break cloud and the fix is in
#9097
- This PR needs to be part of oss v1.30 release.

## Why?
- Backward compatibility and less confusion over how the encoding will
be done.

## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [x] added new unit test(s)
- [ ] added new functional test(s)
@yycptt yycptt changed the base branch from yichao/fix-migration-breaking-change to main January 26, 2026 23:53
@yycptt yycptt force-pushed the fix-migration-breaking-change-cloud branch from 73bd8c9 to 2574162 Compare January 26, 2026 23:55
simvlad pushed a commit that referenced this pull request Jan 27, 2026
## What changed?
- Use plain go struct inside migration workflow activity input output
- Customize the json encoding/decoding for migration execution info and
make it backward & forward compatible.
- This will temporary break cloud and the fix is in
#9097
- This PR needs to be part of oss v1.30 release.

## Why?
- Backward compatibility and less confusion over how the encoding will
be done.

## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [x] added new unit test(s)
- [ ] added new functional test(s)
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