Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Thanks, I hope that this PR will be merged soon. |
|
We appreciate this PR and are working on supporting Pydantic without any upper constraint. First, we need to remove that constraint from one of our dependencies. We are close to addressing this issue without breaking changes. |
|
Hey, it’s a pain with version restrictions in safety currently. This MR is open since end of April. The corresponding issue is open since February. What’s needed to get that into a release? |
When do you think it will be ready? I'd like to re-enable safety. |
|
Thanks @5tefan for providing this PR to solve the blocking issue. Well, looking at the recent dependencies relax changes by @yeisonvargasf in #775 and #776, I get some hope to see it quickly merged. |
|
Thank you for your patience and for contributing this PR. We truly appreciate the community's engagement on this issue, and I apologize for the delay in moving forward with this important change. I'm pleased to confirm that we can now proceed with this PR. The dependency issue that was previously blocking our progress has been resolved. Next steps will be:
Thank you again for your contribution and your patience throughout this process. |
Description
Remove upper version bound for Pydantic.
There are no less than 7 +1s about this in #673.
No background in #655 (refs #620) on why the upper bound on pydantic was put in place. Removed.
There were some deprecation warnings... I resolved the
pydantic_encoderone. Trying to fix theconfigone seems to breaksafety_schemas. I'll let you all handle that one :)safety/safety/formatters/schemas/common.py
Lines 15 to 19 in b1cffbb
Type of Change
Related Issues
Fixes #673
Testing
Ran
pytest.Checklist
Additional Notes