Log message:
py-django-cors-headers: updated to 3.5.0

3.5.0

* Following Django’s example in
  `Ticket 31670 <https://code.djangoproject.com/ticket/31670>`__ for replacing
  the term “whitelist”, plus an aim to make the setting names more
  comprehensible, the following settings have been renamed:

  * ``CORS_ORIGIN_WHITELIST`` -> ``CORS_ALLOWED_ORIGINS``
  * ``CORS_ORIGIN_WHITELIST_REGEX`` -> ``CORS_ALLOWED_ORIGIN_REGEXES``
  * ``CORS_ORIGIN_ALLOW_ALL`` -> ``CORS_ALLOW_ALL_ORIGINS``

  The old names will continue to work as aliases, with the new ones taking
  precedence.

Log message:
py-django-cors-headers: updated to 3.4.0

3.4.0:
* Add Django 3.1 support.

Log message:
py-django-cors-headers: updated to 3.3.0

3.3.0:
* Drop Django 1.11 support. Only Django 2.0+ is supported now.
* Drop the ``providing_args`` argument from ``Signal`` to prevent a deprecation
  warning on Django 3.1.

Log message:
py-django-cors-headers: updated to 3.2.1

3.2.1:
* Update LICENSE file to Unix line endings, fixing issues with license checker
  ``pip-licenses``

Log message:
py-django-cors-headers: updated to 3.2.0

3.2.0:
Converted setuptools metadata to configuration file. This meant removing the \ 
__version__ attribute from the package. If you want to inspect the installed \ 
version, use importlib.metadata.version("django-cors-headers") (docs / \ 
backport).
Support Python 3.8.

Log message:
py-django-cors-headers: updated to 3.1.1

3.1.1:
Support the value file:// for origins, which is accidentally sent by some \ 
versions of Chrome on Android.

3.1.0:
Drop Python 2 support, only Python 3.5-3.7 is supported now.
Fix all links for move from github.com/ottoyiu/django-cors-headers to \ 
github.com/adamchainz/django-cors-headers.

Log message:
py-django-cors-headers: updated to 3.0.2

3.0.2:
* Add a hint to the corsheaders.E013 check to make it more obvious how to
  resolve it.

Log message:
py-django-cors-headers: updated to 3.0.1

3.0.1:

Allow 'null' in CORS_ORIGIN_WHITELIST check.

3.0.0:

CORS_ORIGIN_WHITELIST now requires URI schemes, and optionally ports. This is \ 
part of the CORS specification (Section 3.2) that was not implemented in this \ 
library, except from with the CORS_ORIGIN_REGEX_WHITELIST setting. It fixes a \ 
security issue where the CORS middleware would allow requests between schemes, \ 
for example from insecure http:// Origins to a secure https:// site.

You will need to update your whitelist to include schemes, for example from this:

CORS_ORIGIN_WHITELIST = ['example.com']
...to this:

CORS_ORIGIN_WHITELIST = ['https://example.com']
Removed the CORS_MODEL setting, and associated class. It seems very few, or no \ 
users were using it, since there were no bug reports since its move to abstract \ 
in version 2.0.0 (2017-01-07). If you are using this functionality, you can \ 
continue by changing your model to not inherit from the abstract one, and add a \ 
signal handler for check_request_enabled that reads from your model. Note you'll \ 
need to handle the move to include schemes for Origins.

Log message:
py-django-cors-headers: updated to 2.5.3

2.5.3:
* Tested on Django 2.2. No changes were needed for compatibility.
* Tested on Python 3.7. No changes were needed for compatibility.

Log message:
py-django-cors-headers: updated to 2.5.2

2.5.2:
* Improve inclusion of tests in sdist to ignore .pyc files.

2.5.1:
* Include test infrastructure in sdist to allow consumers to use it.