-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Switch Protobuf checks to non-deprecated bufbuild/buf-action #18037
Conversation
- bufbuild/buf-setup-action [has been deprecated](bufbuild/buf-setup-action@3de295e) since 2024-08-01.
Co-authored-by: Marshall Bowers <[email protected]>
The latest Buf updates on your PR. Results from workflow CI / style (pull_request).
|
I may break this into multiple PRs. One whitespace only commit ( |
@@ -4,2497 +4,2496 @@ package zed.messages; | |||
// Looking for a number? Search "// current max" | |||
|
|||
message PeerId { | |||
uint32 owner_id = 1; | |||
uint32 id = 2; | |||
uint32 owner_id = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way we can keep the protobuf file formatted with 4 spaces? Feels like that matches up with the rest of our code, which all uses 4 spaces.
Couldn't get the core functionality we want (detect breaking changes against branch merge target) so giving up for now. |
Switch to bufbuild/buf-action as the existing actions we're using have been deprecated:
bufbuild/buf-breaking-action@v1
bufbuild/buf-setup-action
See: Deprecation notice (2024-08-01).
Enabling
format
andbreaking_action
but disablelint
as that is a bit aggressive.Release Notes: