chore: bring v0.52.0-beta.2 changelog to main

[julienrbrt]

Description

Closes: #XXXX

---

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, you can find examples of the prefixes below:
• confirmed ! in 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
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• 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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• Improvements
  • Enhanced organization and clarity of the changelog entries for better accessibility.
  • Added new entries highlighting recent features and improvements.
• Chores
  • Removed outdated entries to streamline the changelog and focus on relevant updates.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes involve significant modifications to the CHANGELOG.md file, including the removal of multiple entries under various sections such as "Features," "Improvements," "Bug Fixes," "API Breaking Changes," and "Client Breaking Changes." New entries have been added to the "Features" and "Improvements" sections, reflecting ongoing development in the Cosmos SDK. The overall structure of the changelog has been preserved, ensuring clarity and accessibility for users and developers.

Changes

File	Change Summary
CHANGELOG.md	Removed multiple entries from "Features," "Improvements," "Bug Fixes," "API Breaking Changes," and "Client Breaking Changes." Added new entries in "Features" and "Improvements." Maintained overall structure and organization of the changelog.

Possibly related PRs

• chore: sync changelog with latest releases #21658: This PR also focuses on updates to CHANGELOG.md, specifically synchronizing it with the latest releases, which aligns with the main PR's changes to the changelog entries.
• chore: add releases to changelog #21831: This PR adds new features and improvements to the changelog, which is directly related to the main PR's modifications in the changelog structure and content.
• docs: update package list #22063: This PR updates the package list in the documentation, which may indirectly relate to the changelog updates by reflecting changes in the modules and features documented in the changelog.

Suggested labels

backport/v0.52.x

Suggested reviewers

• sontrinh16
• kocubinski
• auricom
• hieuvubk

---

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3220aab and 91d970c.

📒 Files selected for processing (1)

• CHANGELOG.md (4 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

🔇 Additional comments (8)

CHANGELOG.md (8)

Line range hint 3-5: Major release with significant changes

This release introduces numerous breaking changes and improvements across various modules and components. It's crucial for developers to carefully review all changes and plan for a comprehensive migration strategy when upgrading from previous versions.

---

Line range hint 7-14: Important new features and improvements

The release includes several notable features:

1. New prune CLI command for manual pruning of app store history.
2. Implementation of ADR-028 Derived Addresses.
3. New x/consensus module for maintaining Tendermint consensus parameters.
4. Support for SIGN_MODE_TEXTUAL in transactions.

These additions enhance the functionality and flexibility of the SDK. Developers should familiarize themselves with these new features to leverage them effectively in their applications.

---

Line range hint 16-24: State Machine Breaking Changes

Several modules have undergone state machine breaking changes, including:

1. Changes to x/bank, x/distribution, x/gov, and x/staking modules.
2. Modifications to event emission and balance tracking.
3. Updates to proposal handling in x/gov.

These changes may require updates to existing applications and careful consideration during the upgrade process to ensure compatibility and correct functionality.

---

Line range hint 26-54: API Breaking Changes

Numerous API breaking changes have been introduced across various modules and components. Some key changes include:

1. Modifications to baseapp, client, and server components.
2. Changes to module interfaces and keeper methods.
3. Updates to crypto and store packages.

Developers need to review these changes carefully and update their code accordingly. Special attention should be given to changes in method signatures, interface implementations, and package reorganizations.

---

Line range hint 56-63: Client Breaking Changes

Several client-facing changes have been made, including:

1. Removal of legacy REST API endpoints.
2. Changes to CLI commands and flags.
3. Updates to transaction signing and broadcasting.

These changes may affect existing client implementations and tools. Developers should update their client-side code and documentation to reflect these changes.

---

Line range hint 65-77: Bug Fixes

The release includes numerous bug fixes across various modules and components. Some notable fixes include:

1. Improvements to error handling and panic recovery.
2. Fixes to query result formatting and pagination.
3. Corrections to mathematical operations and gas calculations.

These bug fixes enhance the stability and reliability of the SDK. Developers should review the fixes relevant to their applications and consider updating any workarounds they may have implemented for these issues.

---

Line range hint 79-91: Deprecations and Removals

Several components and functions have been deprecated or removed in this release, including:

1. Removal of x/params module.
2. Deprecation of various helper functions and types.
3. Removal of some CLI commands and flags.

Developers should review their code for usage of deprecated or removed components and update accordingly. It's important to plan for the removal of deprecated features in future releases.

---

Line range hint 1-1341: Comprehensive update with significant improvements and breaking changes

The v0.47.0 release of the Cosmos SDK introduces a wide range of improvements, new features, and breaking changes. Key highlights include the implementation of ADR-028 for derived addresses, a new consensus module, support for SIGN_MODE_TEXTUAL, and numerous performance improvements and bug fixes.

However, the extensive list of breaking changes across state machine, API, and client interfaces necessitates a careful and well-planned upgrade process. Developers should thoroughly review all changes, update their codebase accordingly, and conduct comprehensive testing before upgrading production environments.

This release represents a significant step forward for the Cosmos SDK, but also requires substantial effort from developers to adopt and integrate the changes effectively.

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.