Skip to content

refactor(frontend): rework UPDATE to support subqueries #5699

refactor(frontend): rework UPDATE to support subqueries

refactor(frontend): rework UPDATE to support subqueries #5699

Triggered via pull request November 18, 2024 08:08
Status Failure
Total duration 28s
Artifacts

protobuf-breaking.yml

on: pull_request
Check breaking changes in Protobuf files
17s
Check breaking changes in Protobuf files
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
Check breaking changes in Protobuf files: proto/batch_plan.proto#L176
Field "2" with name "table_version_id" on message "UpdateNode" changed option "json_name" from "exprs" to "tableVersionId".
Check breaking changes in Protobuf files: proto/batch_plan.proto#L176
Field "2" with name "table_version_id" on message "UpdateNode" changed cardinality from "repeated" to "optional with implicit presence".
Check breaking changes in Protobuf files: proto/batch_plan.proto#L176
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.
Check breaking changes in Protobuf files: proto/batch_plan.proto#L176
Field "2" on message "UpdateNode" changed name from "exprs" to "table_version_id".
Check breaking changes in Protobuf files: proto/batch_plan.proto#L178
Field "3" with name "old_exprs" on message "UpdateNode" changed option "json_name" from "returning" to "oldExprs".
Check breaking changes in Protobuf files: proto/batch_plan.proto#L178
Field "3" with name "old_exprs" on message "UpdateNode" changed cardinality from "optional with implicit presence" to "repeated".
Check breaking changes in Protobuf files: proto/batch_plan.proto#L178
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.
Check breaking changes in Protobuf files: proto/batch_plan.proto#L178
Field "3" on message "UpdateNode" changed name from "returning" to "old_exprs".
Check breaking changes in Protobuf files: proto/batch_plan.proto#L180
Field "4" with name "new_exprs" on message "UpdateNode" changed option "json_name" from "tableVersionId" to "newExprs".
Check breaking changes in Protobuf files: proto/batch_plan.proto#L180
Field "4" with name "new_exprs" on message "UpdateNode" changed cardinality from "optional with implicit presence" to "repeated".
Check breaking changes in Protobuf files
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/
Check breaking changes in Protobuf files
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/