Update core & protos

Author: Sushisource

temporalio/bridge/proto/workflow_activation/workflow_activation_pb2.pyi

@@ -53,15 +53,15 @@ class WorkflowActivation(google.protobuf.message.Message):
     This is because:
     * Patches are expected to apply to the entire activation
     * Signal and update handlers should be invoked before workflow routines are iterated. That is to
-      say before the users' main workflow function and anything spawned by it is allowed to continue.
+     say before the users' main workflow function and anything spawned by it is allowed to continue.
     * Local activities resolutions go after other normal jobs because while *not* replaying, they
-      will always take longer than anything else that produces an immediate job (which is
-      effectively instant). When *replaying* we need to scan ahead for LA markers so that we can
-      resolve them in the same activation that they completed in when not replaying. However, doing
-      so would, by default, put those resolutions *before* any other immediate jobs that happened
-      in that same activation (prime example: cancelling not-wait-for-cancel activities). So, we do
-      this to ensure the LA resolution happens after that cancel (or whatever else it may be) as it
-      normally would have when executing.
+     will always take longer than anything else that produces an immediate job (which is
+     effectively instant). When *replaying* we need to scan ahead for LA markers so that we can
+     resolve them in the same activation that they completed in when not replaying. However, doing
+     so would, by default, put those resolutions *before* any other immediate jobs that happened
+     in that same activation (prime example: cancelling not-wait-for-cancel activities). So, we do
+     this to ensure the LA resolution happens after that cancel (or whatever else it may be) as it
+     normally would have when executing.
     * Queries always go last (and, in fact, always come in their own activation)
     * Evictions also always come in their own activation
 

temporalio/bridge/proto/workflow_completion/workflow_completion_pb2.py

@@ -12,6 +12,7 @@ import google.protobuf.internal.containers
 import google.protobuf.message
 
 import temporalio.api.enums.v1.failed_cause_pb2
+import temporalio.api.enums.v1.workflow_pb2
 import temporalio.api.failure.v1.message_pb2
 import temporalio.bridge.proto.workflow_commands.workflow_commands_pb2
 
@@ -75,6 +76,7 @@ class Success(google.protobuf.message.Message):
 
     COMMANDS_FIELD_NUMBER: builtins.int
     USED_INTERNAL_FLAGS_FIELD_NUMBER: builtins.int
+    VERSIONING_BEHAVIOR_FIELD_NUMBER: builtins.int
     @property
     def commands(
         self,
@@ -87,6 +89,10 @@ class Success(google.protobuf.message.Message):
         self,
     ) -> google.protobuf.internal.containers.RepeatedScalarFieldContainer[builtins.int]:
         """Any internal flags which the lang SDK used in the processing of this activation"""
+    versioning_behavior: (
+        temporalio.api.enums.v1.workflow_pb2.VersioningBehavior.ValueType
+    )
+    """The versioning behavior this workflow is currently using"""
     def __init__(
         self,
         *,
@@ -95,11 +101,17 @@ class Success(google.protobuf.message.Message):
         ]
         | None = ...,
         used_internal_flags: collections.abc.Iterable[builtins.int] | None = ...,
+        versioning_behavior: temporalio.api.enums.v1.workflow_pb2.VersioningBehavior.ValueType = ...,
     ) -> None: ...
     def ClearField(
         self,
         field_name: typing_extensions.Literal[
-            "commands", b"commands", "used_internal_flags", b"used_internal_flags"
+            "commands",
+            b"commands",
+            "used_internal_flags",
+            b"used_internal_flags",
+            "versioning_behavior",
+            b"versioning_behavior",
         ],
     ) -> None: ...