deps: update dependency django to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
django (changelog)	>4,<6 → >6,<7

---

Release Notes

django/django (django)

v6.0.4

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• 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.

---

• 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 --upgrade-package django
Using CPython 3.14.4 interpreter at: /opt/containerbase/tools/python/3.14.4/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.11.*'):
  ╰─▶ Because the requested Python version (>=3.11, <4.0) does not satisfy
      Python>=3.12 and django>=6.0.1 depends on Python>=3.12, we can conclude
      that django>=6.0.1 cannot be used.
      And because only the following versions of django are available:
          django<=6
          django==6.0.1
          django==6.0.2
          django==6.0.3
          django==6.0.4
      we can conclude that django>6 cannot be used.
      And because flagsmith-common[common-core] depends on django>6 and your
      project requires flagsmith-common[common-core], we can conclude that
      your project's requirements are unsatisfiable.

      hint: While the active Python version is 3.14, the resolution failed for
      other Python versions supported by your project. Consider limiting your
      project's supported Python versions using `requires-python`.

      hint: The `requires-python` value (>=3.11, <4.0) includes Python
      versions that are not supported by your dependencies (e.g.,
      django>=6.0.1 only supports >=3.12). Consider using a more restrictive
      `requires-python` value (like >=3.12).