Workflow annotations for versioning #548
Description
Is your feature request related to a problem? Please describe.
The new worker versioning-3 implementation requires the annotation of workflows so that if they are pinned, it will not try to move them immediately to a new version, waiting for them to finish before garbage-collecting workers. The benefit of that is that short-running workflows, marked as pinned, do not need to get patched.
Describe the solution you'd like
The goal is to take advantage of code annotations when the language supports them, and the SDK already uses them for other purposes. If that is not the case, a programmatic API should be provided to add this annotation, and it should be invoked during the first workflow task executed by the workflow.
Additional context
Warning
Make sure we mark old APIs deprecated
Per-SDK Tickets
- Go - Support Worker Deployments 3.1 sdk-go#1832
- Java - Support New Worker Versioning API sdk-java#2458
- Core - [Feature Request] Support New Worker Versioning API sdk-core#889
- TypeScript - [Feature Request] Support New Worker Versioning API sdk-typescript#1659
- Python - [Feature Request] Support New Worker Versioning API sdk-python#793
- .NET - [Feature Request] Support New Worker Versioning API sdk-dotnet#437
- Ruby - [Feature Request] Support New Worker Versioning API sdk-ruby#237
- PHP - [Feature Request] Support New Worker Versioning API sdk-php#586