chore: changelog

[boojamya]

Summary by CodeRabbit

• New Features

  • Introduced support for an optional fallback address for fund recovery.
  • Enabled control over which denominations are forwarded.
  • Allowed account registration with a balance without a signer.

• Improvements

  • Upgraded the Cosmos SDK to version v0.50.x.
  • Updated module path to v2 for compliance with Golang conventions.
  • Emitted events for key module actions such as registering and clearing.

• Documentation

  • Updated CHANGELOG.md to include a new "Unreleased" section outlining significant changes.

[coderabbitai]

Walkthrough

The pull request introduces updates to the CHANGELOG.md file, adding a new "Unreleased" section that details significant changes and enhancements. It highlights an upgrade of the Cosmos SDK from version v0.45.x to v0.50.x, along with new features such as optional fallback addresses for fund recovery, control over forwarded denominations, and registration of accounts with balances without a signer. Additionally, it notes improvements like a module path bump to v2 and event emissions for key actions. Previous versions remain unchanged.

Changes

File	Change Summary
CHANGELOG.md	Added "Unreleased" section detailing SDK upgrade to v0.50.x, new features, and improvements. Previous versions v1.1.0 and v1.0.0 remain unchanged.

Poem

🐇 In the meadow where changes bloom,
A new section fills the room.
With upgrades bright, like morning dew,
Fallbacks and controls, all brand new!
Hops of joy, we celebrate,
In our changelog, we elevate! 🌼

---

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

CHANGELOG.md (2)

9-13: Consider adding more details about the fallback address feature.

While the features are well-documented, the fallback address feature (line 11) could benefit from additional context:

• When/how is the fallback address used?
• What happens to existing accounts?
• Are there any security implications?

---

15-18: Fix punctuation and consider adding migration notes.

1. Add a period after "etc" in line 18:

-Emit events for key module actions (registering, clearing, etc). ([#13]
+Emit events for key module actions (registering, clearing, etc.). ([#13]

2. Since this includes a module path bump to v2, consider adding:

• Migration instructions for existing users
• List of specific events being emitted
• Impact on existing implementations

🧰 Tools

🪛 LanguageTool

[style] ~18-~18: In American English, abbreviations like “etc.” require a period.
Context: ... module actions (registering, clearing, etc). ([#13](https://github.com/noble-asset...

(ETC_PERIOD)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4f8f569 and c998fb7.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

CHANGELOG.md

[style] ~18-~18: In American English, abbreviations like “etc.” require a period.
Context: ... module actions (registering, clearing, etc). ([#13](https://github.com/noble-asset...

(ETC_PERIOD)

🔇 Additional comments (2)

CHANGELOG.md (2)

3-4: LGTM! Well-structured changelog format.

The "Unreleased" section is properly placed at the top and follows the Keep a Changelog conventions.

---

5-8: Verify the impact of major SDK upgrade.

The upgrade from Cosmos SDK v0.45.x to v0.50.x is a significant change that spans multiple major versions. This could introduce breaking changes that need careful consideration.

Please ensure:

1. All breaking changes from the Cosmos SDK upgrade have been addressed
2. The module is compatible with the new SDK version
3. All dependencies have been updated to versions compatible with SDK v0.50.x

Consider adding a subsection detailing any breaking changes or migration steps required for this upgrade.