feat!: upgrading django-storages to 1.11.1 #33137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
awais786
changed the title
awais786
changed the title
…ert-32571-django-storages-upgrade
awais786
changed the title
…ert-32571-django-storages-upgrade
iamsobanjaved
approved these changes
Aug 31, 2023
awais786
deleted the
revert-33113-revert-33111-revert-33109-revert-32571-django-storages-upgrade
branch
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrade django-storages
openedx-scorm-xblock 16.0.2 new version released.
Prod logs shows
Now going directly to
1.11.1since it was already deployed on prod.I have reverted this PR yesterday due to scorm issue.