feat: publish v2 protobufs to buf.build/flipt-io/v2#5589
Conversation
|
👋 Hi @markphelps! Thanks for your contribution to this project. It looks like one or more of your commits are missing a DCO (Developer Certificate of Origin) sign-off. The DCO is a simple way for you to certify that you have the right to submit this code under the project's license. How to fix this: # For future commits, use the -s flag
git commit -s -m "Your commit message"
# To sign off on existing commits in this PR
git rebase HEAD~$(git rev-list --count origin/v2..HEAD) --signoff
git push --force-with-leaseThe 📋 View the failing DCO check for more details For more information about the DCO, visit: https://developercertificate.org/ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v2 #5589 +/- ##
=======================================
Coverage 60.40% 60.40%
=======================================
Files 141 141
Lines 13998 13998
=======================================
Hits 8456 8456
Misses 4821 4821
Partials 721 721
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Publish Flipt v2 protobufs under a dedicated Buf module without impacting v1.
Changes
buf.yamlto publish all v2 protos as one module:path: rpc/v2name: buf.build/flipt-io/v2v2*tag workflow in.github/workflows/proto-push.ymlto:rpc/v2rpc/v2againstbranch=v2rpc/v2usingBUF_TOKENNotes
buf.build/flipt-io/fliptunchanged.feat/buf-v2-publishin response to paperclip follow-up.