fix(rest-api): pin workflow-schema protobuf plugins to CI versions#2986
Conversation
Use buf remote plugins for workflow-schema codegen so local regeneration matches the REST/Core CI checks regardless of protoc-gen-go-grpc on PATH.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Summary by CodeRabbit
WalkthroughThe Buf Generation Config Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
🔍 Container Scan Summary
Per-CVE detail lives in the per-service |
🔐 TruffleHog Secret Scan✅ No secrets or credentials found! Your code has been scanned for 700+ types of secrets and credentials. All clear! 🎉 🕐 Last updated: 2026-06-29 19:24:13 UTC | Commit: 082d6d4 |
|
Thanks @kfelternv @thossain-nv , this would definitely help to prevent local regeneration to match CI |
Summary
rest-api/workflow-schema/buf.gen.yamlto buf remote plugins matching CI (protoc-gen-go@v1.36.11,protoc-gen-go-grpc@v1.6.1)protoc-gen-go-grpc(e.g. v1.6.2) from failingCheck REST Core Proto SyncandCheck Protobuf Generated CodeContext
Those checks only rewrite version header comments in a few
*_grpc.pb.gofiles when plugin versions drift. Main already has the correct v1.6.1 headers from #2586; this change stops the drift from recurring.Test plan
make -C rest-api core-protofollowed byscripts/check-repo-clean.sh "REST Core protobuf sync"Check Protobuf Generated Codepasses