@temporalio/core-bridge 1.4.4 → 1.5.1

package/sdk-core/protos/api_upstream/temporal/api/batch/v1/message.proto

@@ -53,12 +53,10 @@ message BatchOperationInfo {
 // Keep the parameter in sync with temporal.api.workflowservice.v1.TerminateWorkflowExecutionRequest.
 // Ignore first_execution_run_id because this is used for single workflow operation.
 message BatchOperationTermination {
-  // Reason of terminate workflows
-  string reason = 1;
   // Serialized value(s) to provide to the termination event
-  temporal.api.common.v1.Payloads details = 2;
+  temporal.api.common.v1.Payloads details = 1;
   // The identity of the worker/client
-  string identity = 3;
+  string identity = 2;
 }
 
 // BatchOperationSignal sends signals to batch workflows.
@@ -79,8 +77,6 @@ message BatchOperationSignal {
 // Keep the parameter in sync with temporal.api.workflowservice.v1.RequestCancelWorkflowExecutionRequest.
 // Ignore first_execution_run_id because this is used for single workflow operation.
 message BatchOperationCancellation {
-  // Reason of cancel workflows
-  string reason = 1;
   // The identity of the worker/client
-  string identity = 2;
+  string identity = 1;
 }

package/sdk-core/protos/api_upstream/temporal/api/command/v1/message.proto

@@ -155,6 +155,13 @@ message UpsertWorkflowSearchAttributesCommandAttributes {
     temporal.api.common.v1.SearchAttributes search_attributes = 1;
 }
 
+message ModifyWorkflowPropertiesCommandAttributes {
+    // If set, update the workflow memo with the provided values. The values will be merged with
+    // the existing memo. If the user wants to delete values, a default/empty Payload should be
+    // used as the value for the key being deleted.
+    temporal.api.common.v1.Memo upserted_memo = 1;
+}
+
 message RecordMarkerCommandAttributes {
     string marker_name = 1;
     map<string, temporal.api.common.v1.Payloads> details = 2;
@@ -255,5 +262,6 @@ message Command {
         UpsertWorkflowSearchAttributesCommandAttributes upsert_workflow_search_attributes_command_attributes = 14;
         AcceptWorkflowUpdateCommandAttributes accept_workflow_update_command_attributes = 15;
         CompleteWorkflowUpdateCommandAttributes complete_workflow_update_command_attributes = 16;
+        ModifyWorkflowPropertiesCommandAttributes modify_workflow_properties_command_attributes = 17;
     }
 }

package/sdk-core/protos/api_upstream/temporal/api/enums/v1/command_type.proto

@@ -47,11 +47,10 @@ enum CommandType {
     COMMAND_TYPE_START_CHILD_WORKFLOW_EXECUTION = 11;
     COMMAND_TYPE_SIGNAL_EXTERNAL_WORKFLOW_EXECUTION = 12;
     COMMAND_TYPE_UPSERT_WORKFLOW_SEARCH_ATTRIBUTES = 13;
-
     // Indicates that an update has been accepted for processing workflow code
     COMMAND_TYPE_ACCEPT_WORKFLOW_UPDATE = 14;
-
     // Indicates that an update has completed and carries either the success or
     // failure outcome of said update.
     COMMAND_TYPE_COMPLETE_WORKFLOW_UPDATE = 15;
+    COMMAND_TYPE_MODIFY_WORKFLOW_PROPERTIES = 16;
 }

package/sdk-core/protos/api_upstream/temporal/api/enums/v1/event_type.proto

@@ -165,4 +165,6 @@ enum EventType {
     // The distinction of external vs. command-based modification is important so the SDK can
     // maintain determinism when using the command-based approach.
     EVENT_TYPE_ACTIVITY_PROPERTIES_MODIFIED_EXTERNALLY = 45;
+    // Workflow properties modified by user workflow code
+    EVENT_TYPE_WORKFLOW_PROPERTIES_MODIFIED = 46;
 }

package/sdk-core/protos/api_upstream/temporal/api/enums/v1/failed_cause.proto

@@ -66,6 +66,7 @@ enum WorkflowTaskFailedCause {
     // The worker encountered a mismatch while replaying history between what was expected, and
     // what the workflow code actually did.
     WORKFLOW_TASK_FAILED_CAUSE_NON_DETERMINISTIC_ERROR = 24;
+    WORKFLOW_TASK_FAILED_CAUSE_BAD_MODIFY_WORKFLOW_PROPERTIES_ATTRIBUTES = 25;
 }
 
 enum StartChildWorkflowExecutionFailedCause {
@@ -94,4 +95,6 @@ enum ResourceExhaustedCause {
     RESOURCE_EXHAUSTED_CAUSE_CONCURRENT_LIMIT = 2;
     // System overloaded.
     RESOURCE_EXHAUSTED_CAUSE_SYSTEM_OVERLOADED = 3;
+    // Namespace exceeds persistence rate limit.
+    RESOURCE_EXHAUSTED_CAUSE_PERSISTENCE_LIMIT = 4;
 }

package/sdk-core/protos/api_upstream/temporal/api/history/v1/message.proto

@@ -192,6 +192,9 @@ message WorkflowTaskCompletedEventAttributes {
     string identity = 3;
     // Binary ID of the worker who completed this task
     string binary_checksum = 4;
+    // ID of the worker who picked up this workflow task, or missing if worker
+    // is not using versioning.
+    temporal.api.taskqueue.v1.VersionId worker_versioning_id = 5;
 }
 
 message WorkflowTaskTimedOutEventAttributes {
@@ -506,6 +509,15 @@ message UpsertWorkflowSearchAttributesEventAttributes {
     temporal.api.common.v1.SearchAttributes search_attributes = 2;
 }
 
+message WorkflowPropertiesModifiedEventAttributes {
+    // The `WORKFLOW_TASK_COMPLETED` event which this command was reported with
+    int64 workflow_task_completed_event_id = 1;
+    // If set, update the workflow memo with the provided values. The values will be merged with
+    // the existing memo. If the user wants to delete values, a default/empty Payload should be
+    // used as the value for the key being deleted.
+    temporal.api.common.v1.Memo upserted_memo = 2;
+}
+
 message StartChildWorkflowExecutionInitiatedEventAttributes {
     // Namespace of the child workflow.
     // SDKs and UI tools should use `namespace` field but server must use `namespace_id` only.
@@ -743,6 +755,7 @@ message HistoryEvent {
         WorkflowUpdateCompletedEventAttributes workflow_update_completed_event_attributes = 48;
         WorkflowPropertiesModifiedExternallyEventAttributes workflow_properties_modified_externally_event_attributes = 49;
         ActivityPropertiesModifiedExternallyEventAttributes activity_properties_modified_externally_event_attributes = 50;
+        WorkflowPropertiesModifiedEventAttributes workflow_properties_modified_event_attributes = 51;
     }
 }
 

package/sdk-core/protos/api_upstream/temporal/api/operatorservice/v1/request_response.proto

@@ -31,15 +31,7 @@ option java_outer_classname = "RequestResponseProto";
 option ruby_package = "Temporal::Api::OperatorService::V1";
 option csharp_namespace = "Temporal.Api.OperatorService.V1";
 
-import "dependencies/gogoproto/gogo.proto";
-import "google/protobuf/timestamp.proto";
-import "google/protobuf/duration.proto";
-
-import "temporal/api/cluster/v1/message.proto";
-import "temporal/api/common/v1/message.proto";
-import "temporal/api/enums/v1/cluster.proto";
 import "temporal/api/enums/v1/common.proto";
-import "temporal/api/version/v1/message.proto";
 
 // (-- Search Attribute --)
 
@@ -84,21 +76,10 @@ message DeleteNamespaceResponse {
     string deleted_namespace = 1;
 }
 
-// (-- api-linter: core::0135::request-unknown-fields=disabled
-//     aip.dev/not-precedent: DeleteNamespace RPC doesn't follow Google API format. --)
-// (-- api-linter: core::0135::request-name-required=disabled
-//     aip.dev/not-precedent: DeleteNamespace RPC doesn't follow Google API format. --)
-message DeleteWorkflowExecutionRequest {
-    string namespace = 1;
-    // Workflow Execution to delete. If run_id is not specified, the latest one is used.
-    temporal.api.common.v1.WorkflowExecution workflow_execution = 2;
-}
-
-message DeleteWorkflowExecutionResponse {
-}
-
 message AddOrUpdateRemoteClusterRequest {
+    // Frontend Address is a cross cluster accessible address.
     string frontend_address = 1;
+    // Flag to enable / disable the cross cluster connection.
     bool enable_remote_cluster_connection = 2;
 }
 
@@ -106,56 +87,35 @@ message AddOrUpdateRemoteClusterResponse {
 }
 
 message RemoveRemoteClusterRequest {
+    // Remote cluster name to be removed.
     string cluster_name = 1;
 }
 
 message RemoveRemoteClusterResponse {
 }
 
-message DescribeClusterRequest {
-    string cluster_name = 1;
-}
-
-message DescribeClusterResponse {
-    map<string,string> supported_clients = 1;
-    string server_version = 2;
-    temporal.api.cluster.v1.MembershipInfo membership_info = 3;
-    string cluster_id = 4;
-    string cluster_name = 5;
-    int32 history_shard_count = 6;
-    string persistence_store = 7;
-    string visibility_store = 8;
-    temporal.api.version.v1.VersionInfo version_info = 9;
-    int64 failover_version_increment = 10;
-    int64 initial_failover_version = 11;
-    bool is_global_namespace_enabled = 12;
-}
-
 message ListClustersRequest {
     int32 page_size = 1;
     bytes next_page_token = 2;
 }
 
 message ListClustersResponse {
-    repeated temporal.api.cluster.v1.ClusterMetadata clusters = 1;
-    bytes next_page_token = 2;
-}
-
-message ListClusterMembersRequest {
-    // (-- api-linter: core::0140::prepositions=disabled
-    //     aip.dev/not-precedent: "within" is used to indicate a time range. --)
-    google.protobuf.Duration last_heartbeat_within = 1 [(gogoproto.stdduration) = true];
-    string rpc_address = 2;
-    string host_id = 3;
-    temporal.api.enums.v1.ClusterMemberRole role = 4;
-    // (-- api-linter: core::0140::prepositions=disabled
-    //     aip.dev/not-precedent: "after" is used to indicate a time range. --)
-    google.protobuf.Timestamp session_started_after_time = 5 [(gogoproto.stdtime) = true];
-    int32 page_size = 6;
-    bytes next_page_token = 7;
+    // List of all cluster information
+    repeated ClusterMetadata clusters = 1;
+    bytes next_page_token = 4;
 }
 
-message ListClusterMembersResponse {
-    repeated temporal.api.cluster.v1.ClusterMember active_members = 1;
-    bytes next_page_token = 2;
+message ClusterMetadata {
+    // Name of the cluster name.
+    string cluster_name = 1;
+    // Id of the cluster.
+    string cluster_id = 2;
+    // Cluster accessible address.
+    string address = 3;
+    // A unique failover version across all connected clusters.
+    int64 initial_failover_version = 4;
+    // History service shard number.
+    int32 history_shard_count = 5;
+    // A flag to indicate if a connection is active.
+    bool is_connection_enabled = 6;
 }

package/sdk-core/protos/api_upstream/temporal/api/operatorservice/v1/service.proto

@@ -66,17 +66,6 @@ service OperatorService {
     rpc DeleteNamespace (DeleteNamespaceRequest) returns (DeleteNamespaceResponse) {
     }
 
-    // DeleteWorkflowExecution asynchronously deletes a specific Workflow Execution (when
-    // WorkflowExecution.run_id is provided) or the latest Workflow Execution (when
-    // WorkflowExecution.run_id is not provided). If the Workflow Execution is Running, it will be
-    // terminated before deletion.
-    // (-- api-linter: core::0135::method-signature=disabled
-    //     aip.dev/not-precedent: DeleteNamespace RPC doesn't follow Google API format. --)
-    // (-- api-linter: core::0135::response-message-name=disabled
-    //     aip.dev/not-precedent: DeleteNamespace RPC doesn't follow Google API format. --)
-    rpc DeleteWorkflowExecution (DeleteWorkflowExecutionRequest) returns (DeleteWorkflowExecutionResponse) {
-    }
-
     // AddOrUpdateRemoteCluster adds or updates remote cluster.
     rpc AddOrUpdateRemoteCluster(AddOrUpdateRemoteClusterRequest) returns (AddOrUpdateRemoteClusterResponse) {
     }
@@ -85,15 +74,7 @@ service OperatorService {
     rpc RemoveRemoteCluster(RemoveRemoteClusterRequest) returns (RemoveRemoteClusterResponse) {
     }
 
-    // DescribeCluster returns information about Temporal cluster.
-    rpc DescribeCluster(DescribeClusterRequest) returns (DescribeClusterResponse) {
-    }
-
     // ListClusters returns information about Temporal clusters.
     rpc ListClusters(ListClustersRequest) returns (ListClustersResponse) {
     }
-
-    // ListClusterMembers returns information about Temporal cluster members.
-    rpc ListClusterMembers(ListClusterMembersRequest) returns (ListClusterMembersResponse) {
-    }
 }

package/sdk-core/protos/api_upstream/temporal/api/schedule/v1/message.proto

@@ -20,6 +20,11 @@
 // OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 // THE SOFTWARE.
 
+// (-- api-linter: core::0203::optional=disabled
+//     aip.dev/not-precedent: field_behavior annotation not available in our gogo fork --)
+// (-- api-linter: core::0203::input-only=disabled
+//     aip.dev/not-precedent: field_behavior annotation not available in our gogo fork --)
+
 syntax = "proto3";
 
 package temporal.api.schedule.v1;
@@ -41,7 +46,8 @@ import "temporal/api/enums/v1/schedule.proto";
 import "temporal/api/workflow/v1/message.proto";
 
 // CalendarSpec describes an event specification relative to the calendar,
-// similar to a traditional cron specification. Each field can be one of:
+// similar to a traditional cron specification, but with labeled fields. Each
+// field can be one of:
 //   *: matches always
 //   x: matches when the field equals x
 //   x/y : matches when the field equals x+n*y where n is an integer
@@ -49,13 +55,14 @@ import "temporal/api/workflow/v1/message.proto";
 //   w,x,y,...: matches when the field is one of the listed values
 // Each x, y, z, ... is either a decimal integer, or a month or day of week name
 // or abbreviation (in the appropriate fields).
-// A second in time matches if all fields match.
+// A timestamp matches if all fields match.
+// Note that fields have different default values, for convenience.
 // Note that the special case that some cron implementations have for treating
 // day_of_month and day_of_week as "or" instead of "and" when both are set is
 // not implemented.
 // day_of_week can accept 0 or 7 as Sunday
-// TODO: add relative-to-end-of-month
-// TODO: add nth day-of-week in month
+// CalendarSpec gets compiled into StructuredCalendarSpec, which is what will be
+// returned if you describe the schedule.
 message CalendarSpec {
     // Expression to match seconds. Default: 0
     string second = 1;
@@ -73,6 +80,51 @@ message CalendarSpec {
     string year = 6;
     // Expression to match days of the week. Default: *
     string day_of_week = 7;
+    // Free-form comment describing the intention of this spec.
+    string comment = 8;
+}
+
+// Range represents a set of integer values, used to match fields of a calendar
+// time in StructuredCalendarSpec. If end < start, then end is interpreted as
+// equal to start. This means you can use a Range with start set to a value, and
+// end and step unset (defaulting to 0) to represent a single value.
+message Range {
+    // Start of range (inclusive).
+    int32 start = 1;
+    // End of range (inclusive).
+    int32 end = 2;
+    // Step (optional, default 1).
+    int32 step = 3;
+}
+
+// StructuredCalendarSpec describes an event specification relative to the
+// calendar, in a form that's easy to work with programmatically. Each field can
+// be one or more ranges.
+// A timestamp matches if at least one range of each field matches the
+// corresponding fields of the timestamp, except for year: if year is missing,
+// that means all years match. For all fields besides year, at least one Range
+// must be present to match anything.
+// TODO: add relative-to-end-of-month
+// TODO: add nth day-of-week in month
+message StructuredCalendarSpec {
+    // Match seconds (0-59)
+    repeated Range second = 1;
+    // Match minutes (0-59)
+    repeated Range minute = 2;
+    // Match hours (0-23)
+    repeated Range hour = 3;
+    // Match days of the month (1-31)
+    // (-- api-linter: core::0140::prepositions=disabled
+    //     aip.dev/not-precedent: standard name of field --)
+    repeated Range day_of_month = 4;
+    // Match months (1-12)
+    repeated Range month = 5;
+    // Match years.
+    repeated Range year = 6;
+    // Match days of the week (0-6; 0 is Sunday).
+    repeated Range day_of_week = 7;
+    // Free-form comment describing the intention of this spec.
+    string comment = 8;
 }
 
 // IntervalSpec matches times that can be expressed as:
@@ -97,24 +149,56 @@ message IntervalSpec {
 // definition of a time zone can change over time (most commonly, when daylight
 // saving time policy changes for an area). To create a totally self-contained
 // ScheduleSpec, use UTC or include timezone_data.
+//
+// For input, you can provide zero or more of: structured_calendar, calendar,
+// cron_string, interval, and exclude_structured_calendar, and all of them will
+// be used (the schedule will take action at the union of all of their times,
+// minus the ones that match exclude_structured_calendar).
+//
+// On input, calendar and cron_string fields will be compiled into
+// structured_calendar (and maybe interval and timezone_name), so if you
+// Describe a schedule, you'll see only structured_calendar, interval, etc.
 message ScheduleSpec {
+    // Calendar-based specifications of times.
+    repeated StructuredCalendarSpec structured_calendar = 7;
+    // cron_string holds a traditional cron specification as a string. It
+    // accepts 5, 6, or 7 fields, separated by spaces, and interprets them the
+    // same way as CalendarSpec.
+    // 5 fields:         minute, hour, day_of_month, month, day_of_week
+    // 6 fields:         minute, hour, day_of_month, month, day_of_week, year
+    // 7 fields: second, minute, hour, day_of_month, month, day_of_week, year
+    // If year is not given, it defaults to *. If second is not given, it
+    // defaults to 0.
+    // Shorthands @yearly, @monthly, @weekly, @daily, and @hourly are also
+    // accepted instead of the 5-7 time fields.
+    // Optionally, the string can be preceded by CRON_TZ=<timezone name> or
+    // TZ=<timezone name>, which will get copied to timezone_name. (There must
+    // not also be a timezone_name present.)
+    // Optionally "#" followed by a comment can appear at the end of the string.
+    // Note that the special case that some cron implementations have for
+    // treating day_of_month and day_of_week as "or" instead of "and" when both
+    // are set is not implemented.
+    // @every <interval>[/<phase>] is accepted and gets compiled into an
+    // IntervalSpec instead. <interval> and <phase> should be a decimal integer
+    // with a unit suffix s, m, h, or d.
+    repeated string cron_string = 8;
     // Calendar-based specifications of times.
     repeated CalendarSpec calendar = 1;
     // Interval-based specifications of times.
     repeated IntervalSpec interval = 2;
-    // Any timestamps matching any of the exclude_calendar specs will be
-    // skipped.
-    repeated CalendarSpec exclude_calendar = 3;
-    // Any timestamps before start_time will be skipped. Together, start_time
-    // and end_time make an inclusive interval.
+    // Any timestamps matching any of exclude_* will be skipped.
+    repeated CalendarSpec exclude_calendar = 3 [deprecated = true]; // use exclude_structured_calendar
+    repeated StructuredCalendarSpec exclude_structured_calendar = 9;
+    // If start_time is set, any timestamps before start_time will be skipped.
+    // (Together, start_time and end_time make an inclusive interval.)
     google.protobuf.Timestamp start_time = 4 [(gogoproto.stdtime) = true];
-    // Any timestamps after end_time will be skipped.
+    // If end_time is set, any timestamps after end_time will be skipped.
     google.protobuf.Timestamp end_time = 5 [(gogoproto.stdtime) = true];
     // All timestamps will be incremented by a random value from 0 to this
-    // amount of jitter. Default: 1 second
+    // amount of jitter. Default: 0
     google.protobuf.Duration jitter = 6 [(gogoproto.stdduration) = true];
 
-    // Time zone to interpret all CalendarSpecs in.
+    // Time zone to interpret all calendar-based specs in.
     //
     // If unset, defaults to UTC. We recommend using UTC for your application if
     // at all possible, to avoid various surprising properties of time zones.
@@ -134,21 +218,17 @@ message ScheduleSpec {
     // at 2:30am and specify a time zone that follows DST, that action will not
     // be triggered on the day that has no 2:30am. Similarly, an action that
     // fires at 1:30am will be triggered twice on the day that has two 1:30s.
+    //
+    // Also note that no actions are taken on leap-seconds (e.g. 23:59:60 UTC).
     string timezone_name = 10;
     bytes timezone_data = 11;
 }
 
 message SchedulePolicies {
     // Policy for overlaps.
-    // Note that this can be changed after a schedule has taken some actions, and we can't
-    // provide 100% sensible semantics for all changes. The most confusing case would be
-    // changes to/from ALLOW_ALL: with that policy multiple scheduled workflows can run
-    // concurrently, but for all other policies only one can run at a time. Changing
-    // between these two classes will leave all workflows with the other class alone.
-    // E.g., if changing from ALLOW_ALL to CANCEL_OTHER, and there are workflows running,
-    // those workflows will not be cancelled. If changing from ALLOW_ALL to SKIP with
-    // workflows running, the running workflows will not cause the next action to be
-    // skipped.
+    // Note that this can be changed after a schedule has taken some actions,
+    // and some changes might produce unintuitive results. In general, the later
+    // policy overrides the earlier policy.
     temporal.api.enums.v1.ScheduleOverlapPolicy overlap_policy = 1;
 
     // Policy for catchups:
@@ -195,10 +275,11 @@ message ScheduleState {
     // If true, do not take any actions based on the schedule spec.
     bool paused = 2;
 
-    // If limited_actions is true, decrement remaining_actions after each action, and do
-    // not take any more scheduled actions if remaining_actions is zero. Actions may still
-    // be taken by explicit request. Skipped actions (due to overlap policy) do not count
-    // against remaining actions.
+    // If limited_actions is true, decrement remaining_actions after each
+    // action, and do not take any more scheduled actions if remaining_actions
+    // is zero. Actions may still be taken by explicit request (i.e. trigger
+    // immediately or backfill). Skipped actions (due to overlap policy) do not
+    // count against remaining actions.
     bool limited_actions = 3;
     int64 remaining_actions = 4;
 }
@@ -258,8 +339,7 @@ message ScheduleInfo {
     google.protobuf.Timestamp create_time = 6 [(gogoproto.stdtime) = true];
     google.protobuf.Timestamp update_time = 7 [(gogoproto.stdtime) = true];
 
-    // Error for invalid schedule. If this is set, no actions will be taken.
-    string invalid_schedule_error = 8;
+    string invalid_schedule_error = 8 [deprecated = true];
 }
 
 message Schedule {
@@ -273,8 +353,7 @@ message Schedule {
 // that's returned in ListSchedules.
 message ScheduleListInfo {
     // From spec:
-    // Some fields are too large/unimportant for the purpose of listing, so we'll clear them
-    // from this copy of spec: exclude_calendar, jitter, timezone_data.
+    // Some fields are dropped from this copy of spec: timezone_data
     ScheduleSpec spec = 1;
 
     // From action:

package/sdk-core/protos/api_upstream/temporal/api/taskqueue/v1/message.proto

@@ -77,7 +77,7 @@ message PollerInfo {
     double rate_per_second = 3;
     // If a worker has specified an ID for use with the worker versioning feature while polling,
     // that id must appear here.
-    string worker_versioning_build_id = 4;
+    VersionId worker_versioning_id = 4;
 }
 
 message StickyExecutionAttributes {
@@ -98,7 +98,7 @@ message VersionIdNode {
 }
 
 // Used by the worker versioning APIs, represents a specific version of something
-// Currently, that's just a whole-worker id. In the future, if we support 
+// Currently, that's just a whole-worker id. In the future, if we support
 // WASM workflow bundle based versioning, for example, then the inside of this
 // message may become a oneof of different version types.
 message VersionId {

package/sdk-core/protos/api_upstream/temporal/api/workflow/v1/message.proto

@@ -56,6 +56,7 @@ message WorkflowExecutionInfo {
     ResetPoints auto_reset_points = 12;
     string task_queue = 13;
     int64 state_transition_count = 14;
+    int64 history_size_bytes = 15;
 }
 
 message WorkflowExecutionConfig {

package/sdk-core/protos/api_upstream/temporal/api/workflowservice/v1/request_response.proto

@@ -222,11 +222,11 @@ message PollWorkflowTaskQueueRequest {
     // "checksum" in this field name isn't very accurate, it should be though of as an id.
     string binary_checksum = 4;
     // If set, the worker is opting in to build-id based versioning and wishes to only
-    // receive tasks that are considered compatible with the version provided in the string.
+    // receive tasks that are considered compatible with the version provided.
     // Doing so only makes sense in conjunction with the `UpdateWorkerBuildIdOrdering` API.
-    // When set, and `binary_checksum` is not, this value should also be considered as the
-    // `binary_checksum`.
-    string worker_versioning_build_id = 5;
+    // When `worker_versioning_id` has a `worker_build_id`, and `binary_checksum` is not
+    // set, that value should also be considered as the `binary_checksum`.
+    temporal.api.taskqueue.v1.VersionId worker_versioning_id = 5;
 }
 
 message PollWorkflowTaskQueueResponse {
@@ -292,6 +292,11 @@ message RespondWorkflowTaskCompletedRequest {
     // Responses to the `queries` field in the task being responded to
     map<string, temporal.api.query.v1.WorkflowQueryResult> query_results = 8;
     string namespace = 9;
+    // If using versioning, worker should send the same id here that it used to
+    // poll for the workflow task.
+    // When `worker_versioning_id` has a `worker_build_id`, and `binary_checksum` is not
+    // set, that value should also be considered as the `binary_checksum`.
+    temporal.api.taskqueue.v1.VersionId worker_versioning_id = 10;
 }
 
 message RespondWorkflowTaskCompletedResponse {
@@ -326,9 +331,9 @@ message PollActivityTaskQueueRequest {
     string identity = 3;
     temporal.api.taskqueue.v1.TaskQueueMetadata task_queue_metadata = 4;
     // If set, the worker is opting in to build-id based versioning and wishes to only
-    // receive tasks that are considered compatible with the version provided in the string.
+    // receive tasks that are considered compatible with the version provided.
     // Doing so only makes sense in conjunction with the `UpdateWorkerBuildIdOrdering` API.
-    string worker_versioning_build_id = 5;
+    temporal.api.taskqueue.v1.VersionId worker_versioning_id = 5;
 }
 
 message PollActivityTaskQueueResponse {
@@ -630,6 +635,19 @@ message TerminateWorkflowExecutionRequest {
 message TerminateWorkflowExecutionResponse {
 }
 
+// (-- api-linter: core::0135::request-unknown-fields=disabled
+//     aip.dev/not-precedent: DeleteNamespace RPC doesn't follow Google API format. --)
+// (-- api-linter: core::0135::request-name-required=disabled
+//     aip.dev/not-precedent: DeleteNamespace RPC doesn't follow Google API format. --)
+message DeleteWorkflowExecutionRequest {
+    string namespace = 1;
+    // Workflow Execution to delete. If run_id is not specified, the latest one is used.
+    temporal.api.common.v1.WorkflowExecution workflow_execution = 2;
+}
+
+message DeleteWorkflowExecutionResponse {
+}
+
 message ListOpenWorkflowExecutionsRequest {
     string namespace = 1;
     int32 maximum_page_size = 2;
@@ -821,6 +839,14 @@ message GetSystemInfoResponse {
 
         // True if server uses protos that include temporal.api.failure.v1.Failure.encoded_attributes
         bool encoded_failure_attributes = 5;
+
+        // True if server supports dispatching Workflow and Activity tasks based on a worker's build_id
+        // (see:
+        // https://github.com/temporalio/proposals/blob/a123af3b559f43db16ea6dd31870bfb754c4dc5e/versioning/worker-versions.md)
+        bool build_id_based_versioning = 6;
+
+        // True if server supports upserting workflow memo
+        bool upsert_memo = 7;
     }
 }
 
@@ -874,6 +900,9 @@ message DescribeScheduleRequest {
 message DescribeScheduleResponse {
     // The complete current schedule details. This may not match the schedule as
     // created because:
+    // - some types of schedule specs may get compiled into others (e.g.
+    //   CronString into StructuredCalendarSpec)
+    // - some unspecified fields may be replaced by defaults
     // - some fields in the state are modified automatically
     // - the schedule may have been modified by UpdateSchedule or PatchSchedule
     temporal.api.schedule.v1.Schedule schedule = 1;
@@ -1059,6 +1088,10 @@ message StartBatchOperationRequest {
     string namespace = 1;
     // Visibility query defines the the group of workflow to do batch operation
     string visibility_query = 2;
+    // Job ID defines the unique ID for the batch job
+    string job_id = 3;
+    // Reason to perform the batch operation
+    string reason = 4;
     // Operation input
     oneof operation {
         temporal.api.batch.v1.BatchOperationTermination termination_operation = 10;
@@ -1068,8 +1101,6 @@ message StartBatchOperationRequest {
 }
 
 message StartBatchOperationResponse {
-    // Batch job id
-    string job_id = 1;
 }
 
 message StopBatchOperationRequest {
@@ -1077,6 +1108,10 @@ message StopBatchOperationRequest {
     string namespace = 1;
     // Batch job id
     string job_id = 2;
+    // Reason to stop a batch operation
+    string reason = 3;
+    // Identity of the operator
+    string identity = 4;
 }
 
 message StopBatchOperationResponse {
@@ -1106,6 +1141,10 @@ message DescribeBatchOperationResponse {
     int64 complete_operation_count = 7;
     // Failure operation count
     int64 failure_operation_count = 8;
+    // Identity indicates the operator identity
+    string identity = 9;
+    // Reason indicates the reason to stop a operation
+    string reason = 10;
 }
 
 message ListBatchOperationsRequest {