chore(deps): bump django from 3.2.24 to 5.2.16 - #6087
Conversation
Bumps [django](https://github.com/django/django) from 3.2.24 to 5.2.16. - [Commits](django/django@3.2.24...5.2.16) --- updated-dependencies: - dependency-name: django dependency-version: 5.2.16 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
🔵 Review postedLast updated: 2026-08-08 05:43 UTC |
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #6087 — Django 3.2.24 → 5.2.16, production dep (pip). Multi-major, 3.2→5.2. CI failing: 3 jobs, all at django.setup().
3.2 is EOL; 5.2.16 fixes CVE-2026-53878, CVE-2026-53877, CVE-2026-48588. Pin-only bump, no migration.
blocking — removed APIs still in use:
| Gone | API | Site |
|---|---|---|
| 4.0 | url() |
search/urls.py:2,11 |
| 4.0 | ugettext |
kolibri_public/views.py:25 |
| 4.0 | jsonb.JSONField |
12 migrations |
| 4.1 | default_app_config |
kolibri_content/__init__.py:1 |
| 5.0 | USE_L10N |
settings.py:268 |
| 5.1 | DEFAULT_FILE_STORAGE |
4 settings modules |
| 5.1 | index_together |
models.py:1578 + 3 migrations |
blocking — CI dies on TypeError: 'class Meta' got invalid attribute(s): index_together. Use Meta.indexes; migrations need AlterIndexTogether→AddIndex (notes).
blocking — DEFAULT_FILE_STORAGE is ignored, not rejected, in 5.1+. default_storage falls back to FileSystemStorage, so uploads land on local disk, not S3/GCS — silently. Convert to STORAGES.
blocking — no declared 5.x support: drf-yasg, django-s3-storage, django-registration, django-mptt, django-cte, jsonfield, django-webpack-loader, django-js-reverse, django-postmark, django-db-readonly.
Stage it: 3.2→4.2 LTS, then 4.2→5.2.
suggestion — requirements.in:43: lift django-pgtrigger<4.12.0 after the upgrade.
Lockfile recompile is clean.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
Bumps django from 3.2.24 to 5.2.16.
Commits
6c8eee4[5.2.x] Bumped version for 5.2.16 release.d5d60ed[5.2.x] Fixed CVE-2026-53878 -- Prevented newlines from being accepted in Dom...6c66eb8[5.2.x] Fixed CVE-2026-53877 -- Prevented heap buffer over-read when creating...721685a[5.2.x] Fixed CVE-2026-48588 -- Prevented caching of responses that set cooki...61a829d[5.2.x] Added stub release notes and release date 5.2.16.21af510[5.2.x] Avoided breaking sha1sum verification in the generated checksum.txt f...039df55[5.2.x] Replaced the defunct pgp.mit.edu keyserver with GitHub for key import.2b3093f[5.2.x] Fixed #29187 -- Fixed flaky receiver count assertion in signals tests.4abc595[5.2.x] Refs #16281 -- Fixed isolation of admin_views.ViewOnSiteTests.f87add9[5.2.x] Added CVE-2026-6873, CVE-2026-7666, CVE-2026-8404, CVE-2026-35193, an...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.