fix: pin pydantic version to less than 2.10.0

[shreysingla11]

Breaking change in pydantic version 2.10.0.

---

Important

Pin pydantic version to <2.10.0 in setup.py to avoid breaking changes.

• Dependencies:
  • Pin pydantic version to >=2.6.4,<2.10.0 in setup.py to avoid breaking changes introduced in version 2.10.0.

^{This description was created by for 71c8773. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
composio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 3, 2025 8:06am

[entelligence-ai-pr-reviews]

LGTM 👍

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 71c8773 in 1 minute and 8 seconds

More details

• Looked at 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. python/setup.py:41

• Draft comment:
  Pinning pydantic to <2.10.0 is correct. Consider adding an inline comment explaining the breaking change in pydantic v2.10.0 for future clarity.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  According to the rules, we should not comment on dependency changes or versions we don't recognize. The comment is purely informative and doesn't require any code changes - it's just suggesting adding documentation. The PR author clearly knew what they were doing since they specifically pinned the version.
  Maybe having documentation about breaking changes in dependencies is actually important for maintainability? Maybe this would save future developers time?
  While documentation can be helpful, the rules clearly state not to comment on dependency changes or make purely informative comments. The version constraint itself serves as documentation of the limitation.
  This comment should be deleted as it violates the rules about not commenting on dependency changes and not making purely informative comments.

2. python/setup.py:41

• Draft comment:
  Pinning pydantic to <2.10.0 is appropriate for avoiding breaking changes in v2.10.0. Consider adding a comment or updating the changelog to document this constraint.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment suggests adding documentation for a dependency version constraint, which is not allowed by the rules. It also provides information about the reason for pinning the version, which is purely informative. Therefore, this comment should be removed.

3. python/setup.py:2

• Draft comment:
  Typo in the module docstring on line 2: 'Setup configuration for compsio core.' should likely read 'Setup configuration for composio core.' to maintain consistency with the project name.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_X1jsL0rcC0M0dg3B

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.