Skip to content

Conversation

@halspang
Copy link
Member

@halspang halspang commented Jan 7, 2026

This field will be used by workers to advertise to the backend what work items it can process. This includes orchestrations, activities, and entities. Currently, orchestrations and activities both take an array for what versions they support despite the fact that multiple versions can't be specified from the workers side. This is also left as an open object so additional support fields can be specified in the future.

This field will be used by workers to advertise to the backend
what work items it can process. This includes orchestrations,
activities, and entities. Currently, orchestrations and activities
both take an array for what versions they support despite the fact
that multiple versions can't be specified from the workers side.
This is also left as an open object so additional support fields
can be specified in the future.

Signed-off-by: Hal Spang <halspang@microsoft.com>
Signed-off-by: Hal Spang <halspang@microsoft.com>
@cgillum
Copy link
Member

cgillum commented Jan 12, 2026

Looks good, but let's wait until the implementations of this new contract is complete before we merge this change (in case we decide to make changes later, prior to the initial release).

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.

3 participants