Shahab TajikandGitHub 87f589f9d3 WorkerVersion field in WorkflowTaskStarted events should never be set in WV3 (#9783) ...

## What changed?
Make sure speculative tasks do not cause the field to be set if WV2 is
not used.

Also a test was added that reproduced the issue, but works fine with the
change.

## Why?
Speculative tasks when completed or failed previously were setting the
WorkerVersion field in their WorkflowTaskStarted events. This is benign
for the execution of WV3-versioned workflows, but if those workflows are
reset, reapplying the events will cause the new workflow to have
AssignedBuildId set WorkerVersion of the latest WorkflowTaskStarted
event.

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

## Potential risks
None.

2026-04-02 16:55:32 +00:00

..

api.go

WorkerVersion field in WorkflowTaskStarted events should never be set in WV3 (#9783)

2026-04-02 16:55:32 +00:00