Field "2" with name "table_version_id" on message "UpdateNode" changed option "json_name" from "exprs" to "tableVersionId".

Field "2" with name "table_version_id" on message "UpdateNode" changed cardinality from "repeated" to "optional with implicit presence".

Field "2" with name "table_version_id" on message "UpdateNode" changed type from "message" 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.

Field "2" on message "UpdateNode" changed name from "exprs" to "table_version_id".

Field "3" with name "old_exprs" on message "UpdateNode" changed option "json_name" from "returning" to "oldExprs".

Field "3" with name "old_exprs" on message "UpdateNode" changed cardinality from "optional with implicit presence" to "repeated".

Field "3" with name "old_exprs" on message "UpdateNode" changed type from "bool" to "message". 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.

Field "3" on message "UpdateNode" changed name from "returning" to "old_exprs".

Field "4" with name "new_exprs" on message "UpdateNode" changed option "json_name" from "tableVersionId" to "newExprs".

Field "4" with name "new_exprs" on message "UpdateNode" changed cardinality from "optional with implicit presence" to "repeated".

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/