Update dependency django to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
django (changelog)	>=5.0.2,<6 -> >=6,<7

---

Release Notes

django/django (django)

v6.0

Compare Source

v5.2.9

Compare Source

v5.2.8

Compare Source

v5.2.7

Compare Source

v5.2.6

Compare Source

---

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.

---

• 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
warning: The `requires-python` specifier (`~=3.11`) in `rcos-io` uses the tilde specifier (`~=`) without a patch version. This will be interpreted as `>=3.11, <4`. Did you mean `~=3.11.0` to constrain the version as `>=3.11.0, <3.12`? We recommend only using the tilde specifier with a patch version to avoid ambiguity.
Using CPython 3.11.14 interpreter at: /opt/containerbase/tools/python/3.11.14/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.11.*'):
  ╰─▶ Because the requested Python version (>=3.11, <4) does not satisfy
      Python>=3.12 and django==6.0 depends on Python>=3.12, we can conclude
      that django==6.0 cannot be used.
      And because only django<=6.0 is available and your project depends
      on django>=6, we can conclude that your project's requirements are
      unsatisfiable.

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