Skip to content

chore(deps): bump django from 3.2.24 to 5.2.16 - #6087

Open
dependabot[bot] wants to merge 1 commit into
unstablefrom
dependabot/pip/django-5.2.16
Open

chore(deps): bump django from 3.2.24 to 5.2.16#6087
dependabot[bot] wants to merge 1 commit into
unstablefrom
dependabot/pip/django-5.2.16

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 8, 2026

Copy link
Copy Markdown
Contributor

Bumps django from 3.2.24 to 5.2.16.

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Aug 8, 2026
@rtibblesbot

rtibblesbot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

🔵 Review posted

Last updated: 2026-08-08 05:43 UTC

@rtibblesbot rtibblesbot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR #6087Django 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 AlterIndexTogetherAddIndex (notes).

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update Python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant