-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: bump sdk and cometbft #8743
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -55,6 +55,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |
* [#8563](https://github.com/osmosis-labs/osmosis/pull/8563) Add additional queries in x/gauges | ||
* [#8726](https://github.com/osmosis-labs/osmosis/pull/8726) fix: multiple temp directories on command executions | ||
* [#8731](https://github.com/osmosis-labs/osmosis/pull/8731) fix: in place testnet logs | ||
* [#8743](https://github.com/osmosis-labs/osmosis/pull/8743) chore: bump sdk and cometbft | ||
|
||
### State Machine Breaking | ||
|
||
Comment on lines
60
to
61
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. State Breaking: Enforce sub-authenticator to be greater than 1 This change could potentially break existing integrations or scripts that rely on the current behavior. It's important to communicate this change clearly to all developers and users who might be affected. Consider adding a brief explanation of why this change was made and how to adapt to it. |
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
State Breaking Changes: SDK v50 and Comet v0.38 upgrade
This is a significant upgrade that may require careful consideration during the upgrade process.
Please ensure that all node operators are aware of this major upgrade and have proper upgrade procedures in place. Consider providing detailed upgrade instructions or linking to them in the changelog.