chore(deps): bump github.com/cometbft/cometbft from 0.38.0-rc3 to 1.0.0-alpha.2

[dependabot]

Bumps github.com/cometbft/cometbft from 0.38.0-rc3 to 1.0.0-alpha.2.

Release notes

Sourced from github.com/cometbft/cometbft's releases.

v1.0.0-alpha.2

See the CHANGELOG for changes available in this pre-release, but not yet officially released.

v1.0.0-alpha.1

See the CHANGELOG for changes available in this pre-release, but not yet officially released.

v0.38.6

See the CHANGELOG for this release.

v0.38.5

See the CHANGELOG for this release.

v0.38.4

See the CHANGELOG for this release.

v0.38.3

See the CHANGELOG for this release.

v0.38.2

See the CHANGELOG for this release.

v0.38.1

See the CHANGELOG for this release.

v0.38.0

See the CHANGELOG for this release.

Changelog

Sourced from github.com/cometbft/cometbft's changelog.

CHANGELOG

v1.0.0-alpha.1

December 4, 2023

This is a major release of CometBFT that includes several substantial changes that aim to reduce bandwidth consumption, enable modularity, improve integrators' experience and increase the velocity of the CometBFT development team, including:

1. Validators now proactively communicate the block parts they already have so others do not resend them, reducing amplification in the network and reducing bandwidth consumption.
2. An experimental feature in the mempool that allows limiting the number of peers to which transactions are forwarded, allowing operators to optimize gossip-related bandwidth consumption further.
3. An opt-in nop mempool, which allows application developers to turn off all mempool-related functionality in Comet such that they can build their own transaction dissemination mechanism, for example a standalone mempool-like process that can be scaled independently of the consensus engine/application. This requires application developers to implement their own gossip/networking mechanisms. See ADR 111 for details.
4. The first officially supported release of the data companion API.
5. Versioning of both the Protobuf definitions and RPC. By versioning our APIs, we aim to provide a level of commitment to API stability while simultaneously affording ourselves the ability to roll out substantial changes in non-breaking releases of CometBFT. See ADR 103 and ADR 107.
6. Moving many Go packages that are currently publicly accessible into the internal directory such that the team can roll out substantial changes in future without needing to worry about causing breakages in users' codebases. The massive surface area of previous versions has in the past significantly hampered the team's ability to roll out impactful new changes to users, as previously such changes required a new breaking release (which currently takes 6 to 12 months to reach production use for many users). See ADR 109 for more details.

None of these changes are state machine-breaking for CometBFT-based networks, but could be breaking for some users who depend on the Protobuf definitions type URLs. See the upgrading guidelines and specific changes below for more details.

NB: This version is still an alpha-series release, which means that API-breaking changes might still be introduced until such time that a release candidate is cut. See RELEASES.md for more information on the stability guarantees we provide for pre-releases.

... (truncated)

Commits

• e42f62b chore: release v1.0.0-alpha.2 (#2621)
• 63471c8 feat(store)!: Support for different key layout (backport #2327) (#2649)
• 081a25f build(deps): Bump docker/login-action from 3.0.0 to 3.1.0 (#2641)
• c850370 build(deps): Bump gonum.org/v1/gonum from 0.14.0 to 0.15.0 (#2643)
• 02f7e46 fix(monitoring): Do not convert ms to ms (backport #2615) (#2617)
• 5a2e40f fix(protos): new buf tag for v1-alpha.2 release
• 636608f fix(e2e): Increase waiting timeout when killing, pausing, or restarting a nod...
• 80ec4d0 fix(e2e): Increase timeout when waiting for new block (backport #2606) (#2609)
• db04c9f docs: Copy description of section on compaction to docs (backport #2600) (#2604)
• fee6d95 docs: format error in ABCI++ specs under commit and listsnapshots section (ba...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)