Previously present field "2" with name "status" on message "BarrierCompleteResponse" was deleted without reserving the name "status".

Previously present field "3" with name "create_mview_progress" on message "BarrierCompleteResponse" was deleted without reserving the name "create_mview_progress".

Previously present field "8" with name "partial_graph_id" on message "BarrierCompleteResponse" was deleted without reserving the name "partial_graph_id".

Previously present field "9" with name "epoch" on message "BarrierCompleteResponse" was deleted without reserving the name "epoch".

Previously present field "2" with name "status" on message "BarrierCompleteResponse" was deleted without reserving the number "2".

Previously present field "3" with name "create_mview_progress" on message "BarrierCompleteResponse" was deleted without reserving the number "3".

Previously present field "8" with name "partial_graph_id" on message "BarrierCompleteResponse" was deleted without reserving the number "8".

Previously present field "9" with name "epoch" on message "BarrierCompleteResponse" was deleted without reserving the number "9".

Field "1" with name "task_id" on message "BarrierCompleteResponse" changed option "json_name" from "requestId" to "taskId".

Field "1" with name "task_id" on message "BarrierCompleteResponse" changed type from "string" to "uint64". See https://developers.google.com/protocol-buffers/docs/proto3#updating for wire compatibility rules and https://developers.google.com/protocol-buffers/docs/proto3#json for JSON compatibility rules.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/