fix(deps): update dependency django-filter to v25

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
django-filter (changelog)	>=23.4,<24 → >=25.2,<26

---

Release Notes

carltongibson/django-filter (django-filter)

v25.2

Compare Source

• Added testing for Django 6.0.

• Dropped support for Django <5.2 LTS

• Dropped support for Python 3.9.

v25.1

Compare Source

• Removed the in-built API schema generation methods, which have been
  deprecated since v23.2.

  You should use drf-spectacular <https://drf-spectacular.readthedocs.io/en/latest/>_
  for generating OpenAPI schemas with DRF.

• Dropped support for EOL Python 3.8.

• Added testing against Python 3.13.

• Added official support for Django 5.2.

v24.3

Compare Source

• Adds official support for Django 5.1.

• Allow using dictionaries for grouped choices on Django 5.0+.

  Thanks to Sævar Öfjörð Magnússon.

• Adds unknown_field_behavior FilterSet option to allowing warning and
  ignore behaviours for unknown field types during FilterSet generation.

  Thanks to Loes.

v24.2

Compare Source

• Fixed a regression in v23.4 where callable choices were incorrectly evaluated
  at filter instantiation, on Django versions prior to 5.0.

  Thanks to Craig de Stigter for the report and reproduce.

v24.1

Compare Source

• Updated supported Python and Django versions, and resolved upcoming Django
  deprecations.

  Required versions are now at least Python 3.8 and Django 4.2.

  Thanks to Michael Manganiello.

• Allowed passing a FilterSet class to the filterset_factory().

  Thanks to Birger Schacht.

• Set empty default value of filterset data to MultiValueDict.

  Thanks to Shlomo Gordon.

• Preserve list values passed to the data dict in CSV widgets.

  Thanks to Bryan Brancotte.

• Updates French and Ukrainian localisations.

  Thanks to Weblate.

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package django-filter
Using CPython 3.13.12
  × No solution found when resolving dependencies:
  ╰─▶ Because wagtail==5.2.8 depends on django-filter>=23.3,<24 and your
      project depends on django-filter>=25.2,<26, we can conclude that your
      project and wagtail==5.2.8 are incompatible.
      And because your project depends on wagtail==5.2.8, we can conclude that
      your project's requirements are unsatisfiable.

[asajjad2]

we would need to upgrade wagtail to minimum wagtail 6.3 to resolve this

[sentry]

Bug: The update to django-filter v25.2 is incompatible with the project's Django v4.2.28, as the new library version only supports Django 5.2 and later.
_{Severity: MEDIUM}

Suggested Fix

To resolve the incompatibility, either downgrade django-filter to a version compatible with Django 4.2 (e.g., ^24.2), or upgrade the project's Django version to 5.2 or newer before updating django-filter.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: pyproject.toml#L24

Potential issue: The `pyproject.toml` file is being updated to use `django-filter`
version `25.2`. According to the library's release notes, this version officially drops
support for Django versions lower than 5.2. The project is currently using Django
`4.2.28`. While the immediate runtime impact is not certain, using a library version
that is explicitly not supported by the project's framework version introduces a
significant risk of unexpected failures, subtle bugs, or breakage in future patch
releases of the dependency. This creates an unsupported and unstable configuration.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The pyproject.toml file updates django-filter to a new version, but the uv.lock file was not regenerated and still points to the old, incompatible version.
_{Severity: HIGH}

Suggested Fix

The dependency upgrade to django-filter 25.2 cannot be completed as-is due to its incompatibility with Django 4.2.29. The change to pyproject.toml should be reverted. If an upgrade is necessary, a version of django-filter compatible with Django 4.2 should be chosen, and both pyproject.toml and uv.lock must be updated accordingly.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: pyproject.toml#L24

Potential issue: The `pyproject.toml` file was updated to require
`django-filter>=25.2,<26`, but the `uv.lock` file was not regenerated. The lock file
still specifies an older version range (`>=23.4,<24`) and resolves to `django-filter
23.5`. This means the intended dependency upgrade has not been applied, and developers
will continue to install the old version. Furthermore, attempting to regenerate the lock
file will cause a failure because `django-filter 25.2` is incompatible with the
project's Django version (`4.2.29`), as it requires Django `5.2` or newer.

[sentry]

Bug: The pyproject.toml dependency change for django-filter is not reflected in the uv.lock file, causing a version mismatch that will either prevent the upgrade or break future builds.
_{Severity: HIGH}

Suggested Fix

Regenerate the uv.lock file by running the appropriate lock command (e.g., uv lock) and commit the updated file. This will synchronize the lock file with the dependency specifications in pyproject.toml.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: pyproject.toml#L24

Potential issue: The `django-filter` dependency was updated in `pyproject.toml` to
version `>=25.2,<26`, but the `uv.lock` file was not regenerated. Consequently,
deployments using the lock file will continue to install the old version,
`django-filter==23.5`, rendering the upgrade ineffective. If the lock file is
regenerated later, the process will fail because `django-filter>=25.2` requires
`Django>=5.2`, while the project uses `django==4.2.29`. This incompatibility will break
the build for anyone attempting to update dependencies.