Skip to content

Conversation

@0xleft
Copy link
Contributor

@0xleft 0xleft commented Oct 28, 2025

Please add the following information to your pull request:

Please describe what your PR is fixing
Upgrading python and django to 3.11 and 5.2 respectively

Concretely, which issues does your PR solve? (Please reference them by typing Fixes/References Inter-Actief/amelie#<issue_id>)
#944

Does your PR change how we process personal data, impact our privacy document, or modify (one of) our data export(s)?
no

Does your PR include any django migrations?
no

Does your PR include the proper translations (did you add translations for new/modified strings)?
yes, I have included the translations / no, my PR does not include translations

Does your PR include CSS changes (and did you run the compile_css.sh script in the scripts directory to regenerate the compiled.css file)?
no, my PR does not include CSS changes

Does your PR need external actions by for example the System Administrators? (Think about new pip packages, new (local) settings, a new regular task or cronjob, new management commands, etc.)?
yes

Did you properly test your PR before submitting it?
no

@0xleft 0xleft linked an issue Oct 28, 2025 that may be closed by this pull request
@0xleft 0xleft changed the title bookworm upgrade + django 5.2 WIP: bookworm upgrade + django 5.2 Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade to Django 5.2 LTS

3 participants