Upgrade to Django 5.2

[dianakhuang]

No description provided.

[Copilot]

Pull request overview

Adjusts dependency constraints and CI configuration in preparation for a Django upgrade, and updates the pinned pip-tools version used for requirements management.

Changes:

• Bumped pip-tools from 7.5.1 to 7.6.0 in the pip-tools requirements set.
• Relaxed the Django upper-bound constraint from <5.0 to <6.0.
• Removed the Django 5.2 job from the unit-test matrix (leaving only the pinned Django run).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
requirements/pip-tools.txt	Updates the pinned pip-tools version used to manage/compile requirements.
requirements/constraints.txt	Relaxes the Django upper-bound constraint (and updates the accompanying comment block).
.github/workflows/unit-tests.yml	Updates CI matrix to no longer run tests against Django 5.2.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (3)

requirements/constraints.txt:24

• requirements/constraints.txt already includes -c common_constraints.txt, and requirements/common_constraints.txt currently constrains Django to Django<6.0 (line 19). Duplicating Django<6.0 here adds a maintenance burden and risks the two constraints diverging; it also contradicts the previous intent to keep this kind of pin in the common constraints file.

# Date: 2026-08-11
# Stay on LTS version
Django<6.0

requirements/pip-tools.txt:13

• requirements/pip-tools.txt has been updated to pip-tools==7.6.0, but requirements/edx/development.txt still pins pip-tools==7.5.1 (see requirements/edx/development.txt:1462) while also indicating it is sourced “via -r requirements/pip-tools.txt”. This mismatch is likely to break dependency installs (conflicting pins) and suggests the compiled requirements weren’t regenerated after the bump.

pip-tools==7.6.0

.github/workflows/unit-tests.yml:25

• The PR is titled “Upgrade to Django 5.2”, but the unit test matrix no longer includes a Django 5.2 job. With only django-version: pinned, CI won’t exercise the upgrade target explicitly, making regressions easier to miss.

        django-version:
          - "pinned"