We should publish our Protobuf definitions to the Buf registry. These should ideally be pushed via CI when we make changes to the protos from our release branches.

[We are not tracking here the issues taking care of publishing tendermint protobufs to the buf repository (v0.34.x to v0.38.x) because, (1) they are not trivial and (2) they are not blockingv1.0. The issue #1402, is in the backlog]

• proto: Rename packages from tendermint -> cometbft #94
• proto: Implement versioning #95
• proto: enum definitions should follow the *_UNSPECIFIED guideline #736
• proto: Rename messages and services to satisfy buf lints #1530
• Implement ADR 107 (using v1beta<N> prefix) #1504
• Update proto file references to follow renaming/versioning #1555
• refactor: split /api into standalone module #1561
• cometbft-rs changes #1834
• proto: Coordinate renaming/versioning changes with users #1403
• proto: Promote the latest message definitions into final v1 packages #1649
• proto: Update README in preparation for publishing to the Buf registry #1650
• feature: Protobuf upgrade #1672 (merge feature branch into main)
• Publish the resulting protobufs to the buf registry #1733
  • buf improvements prior to publishing on BSR #1726
  • Find a solution for dependencies (gogoproto, etc.)
  • (if keeping a copy in our repo) Goal: the files should be the same (published vs. released from Github)
  • [stretch] ideally, automatically via CI when tagging releases or pre-releases (see the pre-release and release workflows in the .github/workflows folder).