-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix CI proto-breaking check on release/*
branches
#8907
Comments
Disabled. Sorry about that. I think the issue is buf checking breakage against master. Do you think we maybe setup buf to check against the release branch based on the branch CI is running against @AmauryM ? |
release/*
branchesrelease/*
branches
Yeah I think it would be useful, to avoid unexpected backports. I re-opened and renamed the issue. |
I think I've got a fix for this in agoric-labs#138. I'll upstream it when I get a chance. |
closed in #11071 |
Summary of Bug
The proto check-breakage CI check doesn't work well on
release/*
branches.Version
0836361
Steps to Reproduce
When backporting PRs from master to
release/*
branches, this check spits non-relevant errors.An example is https://github.com/cosmos/cosmos-sdk/pull/8883/checks?check_run_id=2128071320#step:3:26:
release/v0.42.x
release/v0.42.x
and the Stargate series does NOT have authzIs it comparing to the master branch? Or is it some other bug?
For the time being, I propose to disable the check onDone.release/*
branches (keep on master though)For Admin Use
The text was updated successfully, but these errors were encountered: