Carly de Frondeville fe5a91ce0e Pin workflows across ContinueAsNew and implement Cross-TQ inheritance (#7776) ...

## What changed?
- Updated worker versioning inheritance logic for workflow chains
(parent-child and continue-as-new)
- Replaced deprecated pinned_deployment_version with new
inherited_pinned_version field in workflow execution
- Handled versioning inheritance for retry and cron workflows
- Allow cross-task-queue CaN and Child pinned version inheritance if new
task queue is in the inherited version

## Why?
- Improves versioning behavior consistency across workflow chains by
properly inheriting versioning info from parent/previous runs
- Removes deprecated fields and aligns with new versioning API design
- Fixes edge cases in versioning inheritance for retry and cron
workflows

Basically, we want `PINNED` behavior to carry through parent child
chains, and across the CaN boundary, so that we can roll out a new
behavior for Trampolining in the future, which will not be inherited
across the CaN boundary.

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

## Potential risks
Could break history :P

2025-05-30 02:21:12 +00:00

..

message.go-helpers.pb.go

Remove license header from every file (#7689)

2025-05-01 18:50:21 -07:00

message.pb.go

Pin workflows across ContinueAsNew and implement Cross-TQ inheritance (#7776)

2025-05-30 02:21:12 +00:00