chore: update cosmwasm vm #8734
Conversation
WalkthroughThe pull request includes updates to the changelog, highlighting two main changes. The first is a chore to update the cosmwasm VM, linked to pull request #8734. The second change is a fix that enables the iteration of delegations without errors, associated with pull request #8732. This fix is classified under version v26.0.1, indicating a breaking change in the state machine. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Warning Review ran into problems🔥 ProblemsError running LanguageTool: LanguageTool error: Unknown error Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
CHANGELOG.md (2)
Line range hint
1-5589: Consider adding links to PRs and issuesWhile the changelog is comprehensive, it could be improved by consistently adding links to the corresponding Pull Requests or Issues for each change. This would make it easier for users to find more detailed information about specific changes.
Line range hint
1-5589: Suggestion: Add a table of contentsFor such a long changelog, it might be helpful to add a table of contents at the beginning, linking to each major version. This would improve navigation for users looking for changes in specific versions.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (2)
go.modis excluded by!**/*.modgo.sumis excluded by!**/*.sum,!**/*.sum
📒 Files selected for processing (1)
- CHANGELOG.md (2 hunks)
🔇 Additional comments (7)
CHANGELOG.md (7)
Line range hint
1-3: LGTM: Changelog follows standard formatThe changelog follows the "Keep a Changelog" format and adheres to Semantic Versioning, which is a good practice for maintaining clear and consistent release notes.
Line range hint
5-7: Unreleased changes section presentIt's good to see an "Unreleased" section at the top of the changelog. This allows for documenting changes that are not yet associated with a specific version release.
Line range hint
9-11: State Breaking changes documentedThe changelog clearly identifies state-breaking changes, which is crucial for node operators and developers to be aware of when upgrading.
48-50: New features and improvements highlightedThe changelog effectively highlights new features and improvements, such as the introduction of the taker fee and updates to the CosmWasm VM.
Line range hint
52-54: API breaks clearly markedAPI breaks are clearly marked and explained, which is essential for developers integrating with Osmosis.
63-65: Bug fixes documentedThe changelog includes a section for bug fixes, providing transparency about issues that have been resolved.
Line range hint
71-73: Misc Improvements sectionThe inclusion of a "Misc Improvements" section is helpful for documenting smaller changes that don't fit into other categories.
Closes: #XXX
What is the purpose of the change