-
Notifications
You must be signed in to change notification settings - Fork 4k
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
chore: upgrade dot #33341
chore: upgrade dot #33341
Conversation
bc7a737
to
34b71e1
Compare
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
django-oauth-toolkit==1.6.2 | ||
# django-oauth-toolkit version >=2.0.0 has breaking changes. More details | ||
# mentioned on this issue https://github.com/openedx/edx-platform/issues/32884 | ||
django-oauth-toolkit==1.7.1 |
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.
[Nit] It would be better to constrain to <2.0.0
in case a security patch gets released, like 1.7.2. That hasn't happened yet, but something to consider for future constraints.
Upgrading DOT to
1.7.1
.