chore(deps): update dependency django to v6.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
django (changelog)	>=6.0.6,<6.1.0 → >=6.1,<6.2.0
django (changelog)	>=4.2.0,<5.0.0 → >=6.1,<6.2.0

---

Release Notes

django/django (django)

v6.1

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 these updates again.

---

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

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[dtoxvanilla1991]

@copilot review dependencies latest documentation that are being updated here in PR. Check and validate for any possible migration required and if so, implement minimally viable changes. If breaking changes are in place, stop and provide a detail review only.

[Copilot]

@copilot review dependencies latest documentation that are being updated here in PR. Check and validate for any possible migration required and if so, implement minimally viable changes. If breaking c...

Addressed in d2877ba.

I reviewed the Django 6.1 release/install docs and the relevant impact here is Python support: Django 6.1 supports Python 3.12+, while this repo still supports 3.9–3.11 in CI and packaging. The SDK does not appear to rely on Django-specific APIs that need migration changes, so I applied the minimal safe fix by keeping Django 4.2 for Python <3.12 and allowing Django 6.1 only for Python >=3.12. I also validated the updated markers and ran pytest testv2/testv2_management/test_sdk_tracking.py successfully on Python 3.12.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.