Skip to content

refactor: unify to subscribe mutation via barrier sender #5286

refactor: unify to subscribe mutation via barrier sender

refactor: unify to subscribe mutation via barrier sender #5286

Triggered via pull request September 18, 2024 06:04
Status Failure
Total duration 22s
Artifacts

protobuf-breaking.yml

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

Annotations

3 errors and 2 warnings
Check breaking changes in Protobuf files: proto/stream_service.proto#L12
Previously present field "7" with name "actor_ids_to_pre_sync_barrier_mutation" on message "InjectBarrierRequest" was deleted without reserving the name "actor_ids_to_pre_sync_barrier_mutation".
Check breaking changes in Protobuf files: proto/stream_service.proto#L12
Previously present field "7" with name "actor_ids_to_pre_sync_barrier_mutation" on message "InjectBarrierRequest" was deleted without reserving the number "7".
Check breaking changes in Protobuf files
buf found 2 breaking changes.
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/