Bump django-filter from 2.2.0 to 2.4.0 in /requirements

[dependabot]

Bumps django-filter from 2.2.0 to 2.4.0.

Release notes

Sourced from django-filter's releases.

Version 2.4.0

• SECURITY: Added a MaxValueValidator to the form field for NumberFilter. This prevents a potential DoS attack if numbers with very large exponents were subsequently converted to integers.

  The default limit value for the validator is 1e50.

  The new NumberFilter.get_max_validator() allows customising the used validator, and may return None to disable the validation entirely.

• Added testing against Django 3.1 and Python 3.9.

  In addition tests against Django main development branch are now required to pass.

Version 2.3.0

https://github.com/carltongibson/django-filter/blob/master/CHANGES.rst#version-230-2020-6-5

Changelog

Sourced from django-filter's changelog.

Version 2.4.0 (2020-9-27)

• SECURITY: Added a MaxValueValidator to the form field for NumberFilter. This prevents a potential DoS attack if numbers with very large exponents were subsequently converted to integers.

  The default limit value for the validator is 1e50.

  The new NumberFilter.get_max_validator() allows customising the used validator, and may return None to disable the validation entirely.

• Added testing against Django 3.1 and Python 3.9.

  In addition tests against Django main development branch are now required to pass.

Version 2.3.0 (2020-6-5)

• Fixed import of FieldDoesNotExist. (#1127)
• Added testing against Django 3.0. (#1125)
• Declared support for, and added testing against, Python 3.8. (#1138)
• Fix filterset multiple inheritance bug (#1131)
• Allowed customising default lookup expression. (#1129)
• Drop Django 2.1 and below (#1180)
• Fixed IsoDateTimeRangeFieldTests for Django 3.1
• Require tests to pass against Django master.

Version 2.2 (2019-7-16)

• Added DjangoFilterBackend.get_schema_operation_parameters() for DRF 3.10+ OpenAPI schema generation. (#1086)
• Added lookup_expr to MultipleChoiceFilter (#1054)
• Dropped support for EOL Python 3.4

Version 2.1 (2019-1-20)

• Fixed a regression in FilterView introduced in 2.0. An empty QuerySet was incorrectly used whenever the FilterSet was unbound (i.e. when there were no GET parameters). The correct, pre-2.0 behaviour is now restored.

  A workaround was to set strict=False on the FilterSet. This is no longer necessary, so you may restore strict behaviour as desired.

... (truncated)

Commits

• 7821072 Postpone move to CalVer.
• fd5824e Restore version declaration in setup.py.
• c9daa68 Version 20.9.0.
• c045bbe Droped using bumpversion.
• b1f56ed Use single version reference from main module.
• 451d372 Update docs copyright year.
• 82c9a42 Added MaxValueValidator to NumberFilter.
• 2ebce74 Confirmed compatibility with Python 3.9. (#1270)
• 85c9572 Run tests with GitHub Actions
• d9f389f Update Jinja test dependency.
• 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

You can disable automated security fix PRs for this repo from the Security Alerts page.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
-	Generic Private Key	613009a	config/settings/base.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[vigneshhari]

Looks like there are no breaking changes, merging without testing.