docs: add patch release entries

[johnletey]

No description provided.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces updates to the changelog for versions 8.0.1 and 8.0.2 of the Helium release line. Version 8.0.1 addresses a bug fix related to a surplus of $STAKE tokens due to a genesis file misconfiguration. Version 8.0.2 introduces a consensus-breaking patch to resolve issues encountered during the upgrade to version 8.0.1, particularly concerning the manual initialization of IBC modules due to limitations in IBC-Go v8.

Changes

File Path	Change Summary
.changelog/v8.0.1/bug-fixes/428-surplus-supply.md	Added entry detailing a bug fix for surplus $STAKE tokens due to genesis file misconfiguration.
.changelog/v8.0.1/summary.md	Added changelog entry for version 8.0.1, noting it as a consensus-breaking patch addressing a consensus failure during the upgrade to v8.0.0.
.changelog/v8.0.2/bug-fixes/429-forwarding-initialization.md	Added entry documenting the need for manual initialization of IBC modules due to IBC-Go v8 limitations.
.changelog/v8.0.2/summary.md	Added changelog entry for version 8.0.2, noting it as a consensus-breaking patch addressing a consensus failure from the upgrade to v8.0.1.
CHANGELOG.md	Updated to include version entries for v8.0.1 and v8.0.2, detailing the respective bug fixes and consensus failures related to the Helium release line.

Possibly related PRs

• fix: remove STAKE supply correction in v8 upgrade #428: The changes in this PR involve the removal of the BurnSurplusSupply function, which directly relates to the surplus $STAKE tokens issue addressed in the main PR.

Suggested reviewers

• g-luca

🐰 In the changelog, we hop and play,
Fixing bugs that come our way.
Surplus tokens, oh what a sight,
Manual setups, we’ll get it right!
With each patch, we grow and thrive,
In Helium's world, we come alive! 🌟

---

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.