Add deprecation warning for Pydantic v1 runtime#2833
Conversation
|
Warning Rate limit exceeded@koxudaxi has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 34 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (3)
✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
CodSpeed Performance ReportMerging #2833 will not alter performanceComparing
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2833 +/- ##
=======================================
Coverage 99.52% 99.52%
=======================================
Files 89 89
Lines 13964 13970 +6
Branches 1665 1666 +1
=======================================
+ Hits 13897 13903 +6
Misses 36 36
Partials 31 31
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Breaking Change AnalysisResult: No breaking changes detected Reasoning: This PR adds a deprecation warning when running with Pydantic v1, but does not change any functionality. The tool continues to work exactly as before with Pydantic v1 - users simply receive an informational DeprecationWarning. Deprecation warnings are standard Python practice for notifying users about future changes and are not considered breaking changes. The warning can be suppressed using the existing --disable-warnings flag. No code generation output, templates, API/CLI options, default behavior, or error handling has changed. This analysis was performed by Claude Code Action |
|
🎉 Released in 0.51.0 This PR is now available in the latest release. See the release notes for details. |
Related Issues: #2784