This (draft) PR is the first to providing support for CometBFT v1.0.
The PR appears to be massive but the reason is the tons of newly auto-generated code it introduces. For this reason, please don't review it in one shot; rather use the following description of commits:
Commit 1: Ignore. It is the result of running the protobuf generation on my machine, which produces a few changes in the auto-generated code.
Commit 2: Review. First step: add the logic to handle both Tendermint and CometBFT protobufs. We might decide to deprecate the Tendermint part.
Commit 3: Ignore. The effect in auto-generated code of commit 2.
Commit 4: Review. Adapted protobuf generation tweaks to CombetBFT protos. Commit 2, just copy-pasted the Tendermint ones. This commit allows to see how I adapted them.
Commit 5: Ignore. The effect in auto-generated code of commit 4.
Commit 6: Review. As there are several levels of modules now, the preexisting mechanism to generate the modules was too rigid. This commit introduces and extended version
Commit 7: Ignore. The effect in auto-generated code of commit 6.
Commit 8: Review. Fixes needed in the manual code so that the new proto bufs builds correctly
Commit 9: Review. Changelog.
Note: even if this PR is likely to be ready for review, I decided to leave it a draft PR because we need to discuss whether we should be forking tendermint-rs into cometbft-rs and move this PR there.
[ ] Referenced an issue explaining the need for the change
This (draft) PR is the first to providing support for CometBFT
v1.0
.The PR appears to be massive but the reason is the tons of newly auto-generated code it introduces. For this reason, please don't review it in one shot; rather use the following description of commits:
Note: even if this PR is likely to be ready for review, I decided to leave it a draft PR because we need to discuss whether we should be forking tendermint-rs into cometbft-rs and move this PR there.
.changelog/