Problem: v1.1.0-rc4 is not released

[mmsqe]

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• Have you read the CONTRIBUTING.md?
• Does your PR follow the C4 patch requirements?
• Have you rebased your work on top of the latest master?
• Have you checked your code compiles? (make)
• Have you included tests for any non-trivial functionality?
• Have you checked your code passes the unit tests? (make test)
• Have you checked your code formatting is correct? (go fmt)
• Have you checked your basic code style is fine? (golangci-lint run)
• If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• If your changes affect the client infrastructure, have you run the integration test?
• If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

• Refactor
  • Improved the State Machine functionality for enhanced logic and control flow.

[coderabbitai]

Walkthrough

The version v1.1.0-rc4 introduces substantial updates to the State Machine functionality, marking a pivotal shift in the system's logic and control flow. This version likely enhances the efficiency, reliability, or feature set of the State Machine, potentially impacting how states are defined, transitioned, or managed across the application.

Changes

Files Affected	Summary of Changes
src/state_machine/.../core.py src/state_machine/.../handlers.py	Reworked core logic and event handlers for improved performance and flexibility.
tests/state_machine/...	Added comprehensive tests for new State Machine logic.
docs/state_machine/...	Updated documentation to reflect changes in State Machine functionality.

🐇🌟

In the code where states intertwine,
A rabbit hopped, leaving marks so fine.
With every leap, a change was sown,
A newer, brighter world was shown.
So cheers to v1.1.0-rc4,
Where our code hops higher than before!
🚀🐾

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 08da9cc and d80b0af.

Files selected for processing (1)

• CHANGELOG.md (1 hunks)

Additional comments: 3

CHANGELOG.md (3)

• 5-5: The entry for version v1.1.0-rc4 correctly highlights the significant changes made to the State Machine functionality. It's well-organized and follows the established pattern of the document.
• 5-5: The inclusion of the pull request link (#1318) for the addition of the packet_sequence index in the relayer event under the "State Machine Breaking" category is appropriate. It provides a direct reference to the specific changes made, enhancing the transparency and traceability of the changes.
• 1-8: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [3-1183]

The overall structure and organization of the CHANGELOG.md file are commendable. It provides a clear and detailed record of the project's evolution, enhancing maintainability and understandability. The categorization of changes and the inclusion of direct links to pull requests are best practices that contribute to the project's transparency and traceability.