Cap version of django-cors-header deployed in IDR #169
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
Version 2.5.0 released 7 days ago drops support for Django 1.10 and earlier which breaks the current Web stack.
|
Conflicting PR. Removed from build MANAGEMENT_TOOLS-merge#2188. See the console output for more details.
--conflicts |
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.
The version 2.5.0 of django-cors-headers released 7 days ago drops support for Django 1.10 and earlier which breaks the current Web stack.
Noticed while deploying
prod65. This Travis build should illustrate the problem with the stack trace while deploying IDR.Travis green should confirm this works with the current version of Django asked by OMERO.web.