Skip to content

proto: use a breaking change checker in CI workflow of release branches #8003

@cmwaters

Description

@cmwaters

Summary

All release branches i.e. v0.34.x should never contain any proto-breaking changes. To avoid a situation where this accidentally happens we should use a proto-breaking change checker (like the one provided by buf) in the CI of these release branches


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned

Metadata

Metadata

Assignees

No one assigned

    Labels

    stalefor use by stalebot

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions