mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #2659] Project dependencies may have API risk issues #1671
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1671
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PyDR-Tool on GitHub (Oct 26, 2022).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/2659
Hi, In modoboa, inappropriate dependency versioning constraints can cause risks.
Below are the dependencies and version constraints that the project is using
The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict.
The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.
After further analysis, in this project,
The version constraint of dependency django-reversion can be changed to >=2.0.0,<=5.0.1.
The version constraint of dependency django-otp can be changed to >=0.1.8,<=1.1.3.
The version constraint of dependency djangorestframework-simplejwt can be changed to >=3.1,<=5.2.0.
The version constraint of dependency dnspython can be changed to >=1.13.0,<=2.2.1.
The version constraint of dependency feedparser can be changed to >=6.0.0b1,<=6.0.10.
The version constraint of dependency jsonfield can be changed to >=0.9.14,<=3.1.0.
The version constraint of dependency requests can be changed to >=2.2.0,<=2.15.1.
The version constraint of dependency chardet can be changed to >=2.2.1,<=4.0.0.
The version constraint of dependency redis can be changed to >=2.2.4,<=2.4.9.
The version constraint of dependency redis can be changed to >=3.0.0,<=3.5.3.
The above modification suggestions can reduce the dependency conflicts as much as possible,
and introduce the latest version as much as possible without calling Error in the projects.
The invocation of the current project includes all the following methods.
The calling methods from the django-reversion
The calling methods from the django-otp
The calling methods from the djangorestframework-simplejwt
The calling methods from the dnspython
The calling methods from the feedparser
The calling methods from the jsonfield
The calling methods from the requests
The calling methods from the chardet
The calling methods from the redis
The calling methods from the all methods
@developer
Could please help me check this issue?
May I pull a request to fix it?
Thank you very much.
@stale[bot] commented on GitHub (Dec 26, 2022):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.