Skip to content

Bump buf to v1.71.0#832

Closed
stephanos wants to merge 1 commit into
mainfrom
stephanos/bump-buf-1.71
Closed

Bump buf to v1.71.0#832
stephanos wants to merge 1 commit into
mainfrom
stephanos/bump-buf-1.71

Conversation

@stephanos

Copy link
Copy Markdown
Contributor

What

Bump the pinned buf CLI from v1.27.0v1.71.0 (Makefile buf-install).

Why

Prerequisite for a follow-up PR that adds a custom buf check plugin to enforce that newly added bool capability fields use optional (explicit field presence). Custom check plugins require buf ≥ 1.32 and buf.yaml v2 plugins.

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: the DEFAULT lint category is now STANDARD; 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 plugins wiring come with the linter.

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>
@stephanos stephanos closed this Jul 16, 2026
@stephanos stephanos deleted the stephanos/bump-buf-1.71 branch July 16, 2026 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant