-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use specific safety schema version #618
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -17,7 +17,7 @@ Authlib>=1.2.0 | |||||
rich | ||||||
typer | ||||||
pydantic>=1.10.12 | ||||||
safety_schemas>=0.0.4 | ||||||
safety_schemas==0.0.5 | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🛠️ Refactor suggestion Consider the trade-offs of strict version pinning. While pinning to -safety_schemas==0.0.5
+safety_schemas~=0.0.5 📝 Committable suggestion
Suggested change
|
||||||
typing-extensions>=4.7.1 | ||||||
filelock~=3.12.2 | ||||||
psutil~=6.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Consider using ~= instead of == for version constraint.
While pinning to an exact version ensures stability, using
~=0.0.5
would allow patch updates while preventing minor version changes. This provides a balance between stability and security updates.📝 Committable suggestion