Update aiofiles version constraint in pyproject.toml

[shanto12]

Description

This PR updates the aiofiles version constraint from <24.0.0 to <25.1.0 in pyproject.toml.

Problem

Currently, cognee depends on aiofiles>=23.2.1,<24.0.0, which conflicts with Microsoft agent-framework that requires aiofiles>=24.0.1. This makes it impossible to use cognee alongside Microsoft agent-framework.

Solution

Update the aiofiles upper bound to <25.1.0 to allow compatible versions while still maintaining an upper limit.

Fixes #1829

Type of Change

• Bug fix (non-breaking change that fixes an issue)

Pre-submission Checklist

• I have tested my changes thoroughly before submitting this PR
• This PR contains minimal changes necessary to address the issue/feature

[pull-checklist]

Please make sure all the checkboxes are checked:

• I have tested these changes locally.
• I have reviewed the code changes.
• I have added end-to-end and unit tests (if applicable).
• I have updated the documentation and README.md file (if necessary).
• I have removed unnecessary code and debug statements.
• PR title is clear and follows the convention.
• I have tagged reviewers or team members for feedback.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• pyproject.toml is excluded by !**/*.toml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Hello @shanto12, thank you for submitting a PR! We will respond as soon as possible.

[Vasilije1990]

@siillee can you open a PR and check if tests are passing, and if so we can merge this one

[siillee]

@siillee can you open a PR and check if tests are passing, and if so we can merge this one

@Vasilije1990 Opened a PR on a new branch which triggered CI tests, everything seems to be fine

EDIT: Still working on cleanly merging dev into this branch. After we merge PR about main/dev sync, then we can merge PR regarding this issue.

[dexters1]

Already resolved on the dev branch