fix: rollback version update on api-linter #466
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates api-linter to version v1.56.1 as v.1.57.0 introduced a new requirement for (google.api.field_behavior) = IDENTIFIER to be set on the name field of a proto resource. There is a conflict between buf lint and api-linter due to an update to field_behaviour.proto. An issue has been opened buf as fix is on their side: bufbuild/buf#2474
DavyJ0nes
requested review from
thall,
alethenorio,
odsod and
Edholm
as code owners
radhus
approved these changes
Oct 3, 2023
alethenorio
approved these changes
Oct 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates api-linter to version v1.56.1 as v.1.57.0 introduced a new
requirement for (google.api.field_behavior) = IDENTIFIER to be set on
the name field of a proto resource.
There is a conflict between buf lint and api-linter due to an update to
field_behaviour.proto. An issue has been opened buf as fix is on their side:
bufbuild/buf#2474