-
Notifications
You must be signed in to change notification settings - Fork 16
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
MESSAGE_NO_DELETE rule is not working #140
Comments
The behavior you are expecting should work. If you are not seeing this behavior, then it is likely a configuration issue, but we would need more information to help you diagnose what the issue is. A complete, reproducible example would be ideal, but at the very least we would need to know your buf.yaml, and how you have configured this action in your workflow. |
This is the configuration I'm using in
And this is the workflow configuration:
The buf version is: 1.34.0 but I also tried downgrading to 1.22.0 without success. |
I reproduced your setup and the action correctly failed with the error Example: Going to close this since I am unable to reproduce the error you are reporting given the info you provided. Feel free to re-open if you have a reproducible example that demonstrates incorrect behavior. |
buf-breaking-action passes when I delete a message struct from the protobuf, causing a breaking change further.
Sample:
If I remove the Address message struct, the breaking action still passes, which will provoke a compatibility error with the schema registry in Confluent.
Expected result:
It should fail
The text was updated successfully, but these errors were encountered: