The proto-push workflow is running at the wrong time.

[dwedul-figure]

Summary of Bug

The proto-push workflow is running on merges to main instead of as part of a release.

That means that our published protos don't necessarily represent our most recent release. This can also cause our proto checks to fail erroneously.

Example, #868 was merged to main which caused the new proto files to be pushed. But those protos weren't updated in the release/v1.11.x branch. So any PR based on the release/v1.11.x branch now fails the third-party proto breaking check. It's saying that things have been removed from the proto. But in fact, nothing has been removed, it's just that new additions were pushed up for comparison before they were part of a release.

Version

cab33d8b (and also v1.11.1).

Steps to Reproduce

See https://github.com/provenance-io/provenance/actions/runs/2666663928

Proposed Solution

Move that job into the release.yml workflow and utilize the setup/variables in there to do that job during a release (instead of on push to main).

---

For Admin Use

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