-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Freeze package versions in requirements-*.txt #755
base: master
Are you sure you want to change the base?
Conversation
requirements.txt
Outdated
requests>=2.32.3,<3 | ||
urllib3>=2.0.5,<3 | ||
aiohttp >=3.10.9 | ||
future | ||
aiohttp >=3.10.9, <4 | ||
future==1.0.0 | ||
pydantic >=2.0.3, <3 | ||
aenum >= 3.1.11 | ||
python_dateutil >= 2.5.3 | ||
Deprecated | ||
aenum >= 3.1.11, <4 | ||
python_dateutil >= 2.5.3, <3 | ||
Deprecated==1.2.18 |
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.
about future
, Deprecated
If this completely fixes the version, it may cause conflicts with other libraries on the user's side, and the user may not be able to apply security patches. Please only set upper and lower bounds if necessary.
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.
Deprecated>=1.2.18
future >= 1.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.
can you resolve conflict at first?
This PR addresses the issue of potential breaking changes in our dependencies by freezing the current package versions in the requirements-*.txt files.