open
open copied to clipboard
Bump django-cors-headers from 3.1.0 to 3.7.0
Bumps django-cors-headers from 3.1.0 to 3.7.0.
Changelog
Sourced from django-cors-headers's changelog.
3.7.0 (2021-01-25)
- Support Django 3.2.
3.6.0 (2020-12-13)
- Drop Python 3.5 support.
- Support Python 3.9.
3.5.0 (2020-08-25)
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_REGEX_WHITELIST
->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.
3.4.0 (2020-06-19)
- Drop Django 2.0 and 2.1 support.
3.4.0 (2020-06-15)
- Add Django 3.1 support.
3.3.0 (2020-05-18)
- Drop Django 1.11 support. Only Django 2.0+ is supported now.
- Drop the
providing_args
argument fromSignal
to prevent a deprecation warning on Django 3.1.3.2.1 (2020-01-04)
- Update LICENSE file to Unix line endings, fixing issues with license checker
pip-licenses
([Issue #477](adamchainz/django-cors-headers#477)).3.2.0 (2019-11-15)
- Converted setuptools metadata to configuration file. This meant removing the
__version__
attribute from the package. If you want to inspect the installed version, useimportlib.metadata.version("django-cors-headers")
(docs / backport).- Support Python 3.8.
3.1.1 (2019-09-30)
... (truncated)
Commits
8419921
Version 3.7.0eb2944e
Add an AppConfig (#618)b3ab8d2
Git ignore coverage files (#617)46df1d6
Support Django 3.2 (#616)b3c2db1
Upgrade requirements (#614)bdb44b6
Move code coverage collection to codecov (#612)ecab576
[pre-commit.ci] pre-commit autoupdate (#611)50ecc7f
Upgrade requirements (#610)a24500c
Upgrade requirements (#609)d0bd527
Update LICENSE year to 2021 (#608)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language -
@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)