build: use cometbft in v0.45

[julienrbrt]

Description

ref: #14870

TODO

• Wait for v0.34 tag
• Cherry-pick fix: double close #13400 updating checksums.
• Bump to go.19 (mention coordinated upgrade required if go bump)
• Add release notes

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[julienrbrt]

reopening when ready

[julienrbrt]

Due to https://github.com/cometbft/cometbft/blob/v0.34.27-alpha.2/go.mod#L55, we need to cherry-pick 0b64514 in v0.45 too.

[julienrbrt]

When we get a final v0.34.27 we can tag final. For now, tagged a v0.45.15-rc.0 for already testing on mainnets.

[troian]

@julienrbrt v0.34.27 is out. mind cutting v0.45.15?

[julienrbrt]

@julienrbrt v0.34.27 is out. mind cutting v0.45.15?

We are still running a bunch of tests on final v0.45.15 and v0.46.11 and we will tag both.
Probably tomorrow or at worse begin next week.

[troian]

@julienrbrt cool, thank you!

[troian]

hey @julienrbrt. should we expect this to come or there are some issues revealing during testing?

[julienrbrt]

hey @julienrbrt. should we expect this to come or there are some issues revealing during testing?

We've already tagged v0.46.11, v0.45.15 will come later today/tomorrow 👍🏾