Bump django-cors-headers from 3.14.0 to 4.2.0

[dependabot[bot]]

Bumps django-cors-headers from 3.14.0 to 4.2.0.

Changelog

Sourced from django-cors-headers's changelog.

4.2.0 (2023-07-10)

• Drop Python 3.7 support.

4.1.0 (2023-06-14)

• Support Python 3.12.

4.0.0 (2023-05-12)

• 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/issues/745) <https://github.com/adamchainz/django-cors-headers/pull/745>__ and jjurgens0 in PR [#833](https://github.com/adamchainz/django-cors-headers/issues/833) <https://github.com/adamchainz/django-cors-headers/pull/833>__.

• Remove three headers from the default "accept list": accept-encoding, dnt, and origin. 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) <https://github.com/adamchainz/django-cors-headers/issues/842>__.

• Drop the CORS_REPLACE_HTTPS_REFERER setting and CorsPostCsrfMiddleware. 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.

Commits

• 26e0533 Version 4.2.0
• 188ca87 Exclude tests from sdist
• 380bd70 [pre-commit.ci] pre-commit autoupdate (#875)
• b0cc36c Drop Python 3.7 support (#877)
• d6048cb [pre-commit.ci] pre-commit autoupdate (#874)
• 63ab056 [pre-commit.ci] pre-commit autoupdate (#873)
• bd0724a Upgrade requirements (#872)
• 5c5172a Version 4.1.0
• 187ac13 Support Python 3.12 (#871)
• 5ed08ab [pre-commit.ci] pre-commit autoupdate (#870)
• 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)