fix(deps): update dependency django-cors-headers to v4 #4350
+8
−7
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.
This PR contains the following updates:
^3.6.0
->^4.0.0
Release Notes
adamchainz/django-cors-headers (django-cors-headers)
v4.6.0
Compare Source
v4.5.0
Compare Source
Drop Python 3.8 support.
Support Python 3.13.
v4.4.0
Compare Source
v4.3.1
Compare Source
Fixed ASGI compatibility on Python 3.12.
Thanks to Adrian Capitanu for the report in
Issue #​908 <https://github.com/adamchainz/django-cors-headers/issues/908>
__ and Rooyal inPR #​911 <https://github.com/adamchainz/django-cors-headers/pull/911>
__.v4.3.0
Compare Source
Avoid adding the
access-control-allow-credentials
header to unallowed responses.Thanks to Adam Romanek in
PR #​888 <https://github.com/adamchainz/django-cors-headers/pull/888>
__.Support Django 5.0.
v4.2.0
Compare Source
v4.1.0
Compare Source
v4.0.0
Compare Source
Add
CORS_ALLOW_PRIVATE_NETWORK
setting, which enables support for the Local Network Access draft specification.Thanks to Issac Kelly in
PR #​745 <https://github.com/adamchainz/django-cors-headers/pull/745>
__ and jjurgens0 inPR #​833 <https://github.com/adamchainz/django-cors-headers/pull/833>
__.Remove three headers from the default "accept list":
accept-encoding
,dnt
, andorigin
.These are
Forbidden header names <https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_header_name>
__, which means requests JavaScript can never set them.Consequently, allowing them via CORS has no effect.
Thanks to jub0bs for the report in
Issue #​842 <https://github.com/adamchainz/django-cors-headers/issues/842>
__.Drop the
CORS_REPLACE_HTTPS_REFERER
setting andCorsPostCsrfMiddleware
.Since Django 1.9, the
CSRF_TRUSTED_ORIGINS
setting has been the preferred solution to making CSRF checks pass for CORS requests.The removed setting and middleware only existed as a workaround for Django versions before 1.9.
Add async support to the middleware, reducing overhead on async views.
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.