docs: bring v5.1.1 changelog to main

[mpoke]

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

• Bug Fixes

  • Corrected inaccuracies in message definitions within the provider module's protocol files, enhancing communication reliability and functionality.

• Documentation

  • Updated changelog to reflect version 5.1.1, summarizing significant API and state breaking changes related to the provider module.

[coderabbitai]

Walkthrough

Walkthrough

The update to version 5.1.1 addresses inaccuracies in the message definitions within the proto files of the provider module. This revision ensures improved alignment of the protocol buffers with the intended functionality, enhancing the module's API integrity and reliability in interchain communications. The updates are linked to identified issues, reinforcing the system's overall data exchange integrity and operational reliability.

Changes

Files	Change Summary
.changelog/v5.1.1/api-breaking/provider/2095-proto-message-fix.md	Corrected message definitions in proto files to improve API functionality and communications.
.changelog/v5.1.1/state-breaking/provider/2095-proto-message-fix.md	Fixed inaccurate message definitions in proto files to enhance data integrity and module reliability.
CHANGELOG.md	Updated to include version v5.1.1, outlining API BREAKING and STATE BREAKING changes related to provider module.
.changelog/v5.1.1/summary.md	Introduced entry for version updates, documenting changes in a structured timeline.

---

Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3fa4181 and fdb9be0.

Files selected for processing (4)

• .changelog/v5.1.1/api-breaking/provider/2095-proto-message-fix.md (1 hunks)
• .changelog/v5.1.1/state-breaking/provider/2095-proto-message-fix.md (1 hunks)
• .changelog/v5.1.1/summary.md (1 hunks)
• CHANGELOG.md (1 hunks)

Files skipped from review due to trivial changes (3)

• .changelog/v5.1.1/api-breaking/provider/2095-proto-message-fix.md
• .changelog/v5.1.1/state-breaking/provider/2095-proto-message-fix.md
• .changelog/v5.1.1/summary.md

Additional comments not posted (3)

CHANGELOG.md (3)

3-18: Changelog entry is consistent.

The changelog entry for version v5.1.1 is consistent with the previous entries in terms of format and structure.

---

11-11: Link to the pull request is correct.

The link to the pull request (#2095) is correctly formatted and functional.

Also applies to: 17-17

---

3-18: Overall quality of the changelog entry is good.

The changelog entry for version v5.1.1 is clear and provides necessary information about the changes.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 1

[coderabbitai]

Correct spelling errors in descriptions.

The word "defitions" should be corrected to "definitions".

-  - Fix incorrect message defitions in the proto files of the provider module
+  - Fix incorrect message definitions in the proto files of the provider module

Also applies to: 16-16

[p-offtermatt]

I think our spellchecker bot will pick this up after its merged

[coderabbitai]

@p-offtermatt, understood. Just to confirm, is the spellchecker bot configured to catch such errors in the changelog? If so, we can proceed as you suggested. If there's anything specific I should check or configure, please let me know.