Bump buf to v1.71.0#832
Closed
stephanos wants to merge 1 commit into
Closed
Conversation
Update the pinned buf CLI version from v1.27.0 to v1.71.0. This is a prerequisite for adding custom check plugins (buf.yaml v2 `plugins`), which require buf >= 1.32. Backwards-compatible: `buf lint` and `buf breaking` continue to pass against the existing v1 config (buf emits a non-fatal deprecation notice for the DEFAULT lint category, cleaned up in the follow-up v2 migration). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
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.
What
Bump the pinned buf CLI from
v1.27.0→v1.71.0(Makefilebuf-install).Why
Prerequisite for a follow-up PR that adds a custom buf check plugin to enforce that newly added
boolcapability fields useoptional(explicit field presence). Custom check plugins require buf ≥ 1.32 andbuf.yamlv2plugins.Splitting the bump out so it can land and bake independently of the linter change.
Validation
With buf 1.71.0 against the current (unchanged) v1 config:
buf lint→ passes (one non-fatal deprecation notice: theDEFAULTlint category is nowSTANDARD; cleaned up in the v2 migration that ships with the linter PR).buf breaking --against ...#branch=main→ passes.No config changes in this PR — the v2 migration and
pluginswiring come with the linter.