Update dependency django-cors-headers to v4.3.1 - autoclosed #80
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/django-cors-headers-4.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==4.2.0
->==4.3.1
Release Notes
adamchainz/django-cors-headers (django-cors-headers)
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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
8c2444a57b
tof5b0ba5783
f5b0ba5783
tob83a7d3236
Update dependency django-cors-headers to v4.3.0to Update dependency django-cors-headers to v4.3.1Update dependency django-cors-headers to v4.3.1to Update dependency django-cors-headers to v4.3.1 - autoclosedPull request closed