Uncap Pydantic Version

[PGijsbers]

I couldn't find the reason for the constraint to <2.7, local unit tests look fine with the newer version.

Summary by CodeRabbit

Chores

• Updated pydantic dependency to support newer versions, expanding compatibility.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The pydantic dependency constraint in pyproject.toml was relaxed by removing the upper version bound, changing from pydantic<2.7 to pydantic. This permits installation of any pydantic version without the previous maximum version restriction.

Changes

Cohort / File(s)	Change Summary
Dependency version constraint update pyproject.toml	Removed upper version bound on pydantic dependency; changed from pydantic<2.7 to pydantic

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit's release, oh what cheer! ✨
Pydantic now flows, both far and near
No bounds to constrain, no limits to fear
Version flexibility, crystal clear! 🐰

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: removing the version upper bound constraint (uncapping) from the Pydantic dependency in pyproject.toml.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-pydantic

---

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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

pyproject.toml (1)

17-17: Consider adding an upper bound to prevent unexpected major version upgrades.

Removing the version constraint entirely allows any future version of Pydantic to be installed, including potential v3 releases which could introduce breaking changes. While Pydantic does not intentionally make breaking changes in minor releases of V2 and all Pydantic versions above 1.0.0 are compatible with FastAPI, a constraint like pydantic>=2,<3 would protect against major version breaks while allowing flexibility within the v2.x series.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e1c3e0f and d103d83.

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: python
• GitHub Check: compare-php

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@e1c3e0f). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #220   +/-   ##
=======================================
  Coverage        ?   92.54%           
=======================================
  Files           ?       51           
  Lines           ?     1851           
  Branches        ?      144           
=======================================
  Hits            ?     1713           
  Misses          ?       97           
  Partials        ?       41           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.