bufbuild
[DO NOT MERGE] Add static buf.yaml files for `protovalidate` and `protovalidate-testing`
Similar treatment than #579, waiting if/when protovalidate moves to v2: https://github.com/bufbuild/protovalidate/pull/233
The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).
| Build | Format | Lint | Breaking | Updated (UTC) |
|---|---|---|---|---|
✅ passed | ✅ passed | ✅ passed | ✅ passed | May 14, 2025, 7:34 PM |
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Following up on this -- I recently put up https://github.com/bufbuild/protovalidate/pull/366 to migrate to a v2 buf.yaml file, unaware of some of the obstacles. What is the status of being able to support it? @unmultimedio
Following up on this -- I recently put up bufbuild/protovalidate#366 to migrate to a v2 buf.yaml file, unaware of some of the obstacles. What is the status of being able to support it? @unmultimedio
Sure we're ready if you wanna move to v2, see this comment https://github.com/bufbuild/protovalidate/pull/233#issuecomment-2263399945. If we decide to do it, this PR should be merged first, and then you can bump pv to v2.
Lmk to update+merge this one first.
Sure we're ready if you wanna move to
v2, see this comment bufbuild/protovalidate#233 (comment). If we decide to do it, this PR should be merged first, and then you can bump pv to v2.Lmk to update+merge this one first.
Great. I'm ready if others think we're ok @rodaine @timostamm
Think we're ready to when you are @unmultimedio thanks!
@smaye81 this is merged! feel free to merge yours, and I'll ping you when the next release for both pv and pvt is being synced here, to sanity check this went fine.
Just merged #366 @unmultimedio. Lmk if things look ok whenever.
Sure, this repo will pick things up the next semver release.