fix:allow newer pyee

[JarbasAl]

last backwards compatible version

relates to #123

Summary by CodeRabbit

• Chores
  • Updated the version constraint for the pyee package, allowing for a broader range of compatible versions.

[coderabbitai]

Walkthrough

The requirements.txt file has been updated to modify the version constraint for the pyee package. The new constraint allows for a broader range of versions, changing from pyee>=8.1.0, <9.0.0 to pyee>=8.1.0, <12.0.0. No other dependencies or constraints were altered in this update.

Changes

File	Change Summary
requirements.txt	Updated version constraint for pyee from >=8.1.0, <9.0.0 to >=8.1.0, <12.0.0

Poem

In the garden of code, we hop and play,
With pyee now free to grow and sway.
From eight to twelve, it leaps with glee,
A broader range for you and me!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between dfdc584 and a215a93.

📒 Files selected for processing (1)

• requirements.txt (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

requirements.txt (1)

4-4: Approve change with caution: Verify compatibility with newer pyee versions

The update to allow newer versions of pyee (up to <12.0.0) aligns with the PR objectives. However, the significant increase in the upper bound raises some concerns:

1. There might be breaking changes in pyee versions 9, 10, or 11 that could affect the project.
2. The large version jump increases the risk of introducing incompatibilities.

To ensure the change doesn't introduce issues:

1. Please verify if there are any known breaking changes in pyee versions 9, 10, and 11 that might affect this project.
2. Run the project's test suite against the newer pyee versions to confirm compatibility.

You can use the following script to check for potential breaking changes in the pyee changelog:

If any breaking changes are found, please review them carefully and consider adjusting the version constraint accordingly.

---

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.