Skip to content

chore(proto): regenerate stubs after a protovalidate dep bump - #823

Closed
lakhansamani wants to merge 1 commit into
mainfrom
chore/regen-client-stubs
Closed

lakhansamani wants to merge 1 commit into
mainfrom
chore/regen-client-stubs

Conversation

@lakhansamani

Copy link
Copy Markdown
Contributor

Unblocks CI. Found while #821 went red on Lint & breaking for a reason that had nothing to do with its own diff.

buf dep update resolves a newer buf.build/bufbuild/protovalidate, which moved its documentation URLs:

- * [see our documentation](https://buf.build/docs/protovalidate/schemas/custom-rules/)
+ * [see our documentation](https://protovalidate.com/schemas/custom-rules/)

Seven doc comments in gen/ts/buf/validate/validate_pb.ts, plus the proto/buf.lock digest. No API, field or wire change.

This was latent on main: buf.yml triggers on changes to proto/**, gen/** or the Makefile, so the staleness gate stayed quiet until a PR touched one of those — #821 edits the Makefile to add a test target — and then failed pointing at the wrong change.

Verification

  • make proto-check, make proto-check-clients, make proto-lint: all pass.
  • Regeneration is stable — re-running make proto-gen and make proto-gen-clients after committing leaves the tree clean, so this is not a moving target.
  • go build ./..., go vet ./...: clean.

buf dep update picks up a newer buf.build/bufbuild/protovalidate, which
moved its documentation URLs from buf.build/docs/protovalidate/... to
protovalidate.com/..., changing seven doc comments in the generated TS.

No API, field or wire change -- comments and the buf.lock digest only.

Latent on main: buf.yml runs on changes to proto/, gen/ or the Makefile,
so the staleness gate stayed quiet until a PR touched one of those and
then failed for a reason unrelated to its own diff.
@lakhansamani

Copy link
Copy Markdown
Contributor Author

Superseded by #824, which carries this change unmodified alongside the other three commits in one PR — no merge-order dependency between them.

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