docs: add changelog for v4.5.0 release

[sainoe]

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 docs: prefix in the PR title
• [ ] targeted the correct branch (see PR Targeting)
• [ ] provided a link to the relevant issue 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 docs: prefix in the PR title
• [ ] Confirmed all author checklist items have been addressed
• [ ] Confirmed that this PR only changes documentation
• [ ] Reviewed content for consistency
• [ ] Reviewed content for spelling and grammar
• [ ] Tested instructions (if applicable)
• [ ] Checked that the documentation website can be built and deployed successfully (run make build-docs)

Summary by CodeRabbit

• New Features

  • Enhanced IBC transfer packet handling with the addition of a memo field for consumer chain identification.
  • Updated functionality for identifying the source of ICS rewards from the memo in IBC transfer packets.

• Bug Fixes

  • Resolved issue with duplicate event emissions on cached context.

• Breaking Changes

  • Noted state-breaking changes that may affect existing functionality or data structures related to IBC transfers.

[coderabbitai[bot]]

📝 Walkthrough

📝 Walkthrough

## Walkthrough The changes in version 4.5.0 primarily focus on enhancing the handling of IBC transfer packets related to ICS rewards. The memo field in these packets is now populated with the consumer chain ID, improving the identification of the consumer by the provider. Additionally, a bug fix has been implemented to eliminate duplicate event emissions on cached context. These modifications are categorized as state-breaking changes, indicating potential impacts on existing functionality. ## Changes | File Path | Change Summary | |------------------------------------------------|---------------------------------------------------------------------------------------------------------| | .changelog/v4.5.0/features/2290-add-memo-to-ICS-rewards.md | Updated IBC transfer packet handling to include consumer chain ID in the memo field for reward tracking. | | .changelog/v4.5.0/summary.md | Added changelog entry for v4.5.0, summarizing enhancements to IBC transfer packets and bug fixes. | | CHANGELOG.md | Documented key updates in v4.5.0, including memo population and bug fix for event emissions. | ## Possibly related issues - **cosmos/interchain-security#1634**: The changes in this PR address the issue of identifying consumer chains for reward allocation by utilizing the memo field in IBC transfer packets. ## Possibly related PRs - **#2016**: Updates changelog for ICS v4.3.1, relevant to IBC transfer packet handling and rewards. - **#2037**: Updates documentation for ICS v4.4.0, which includes changes to the provider's functionality impacting reward identification. - **#2059**: Brings changelog for v4.4.0 to the main branch, including updates related to provider functionality and reward identification. - **#2096**: Adds entry for version 5.1.0 in the changelog, which includes significant changes to the provider module that may relate to ICS rewards handling. ## Suggested labels `C:Docs`

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.