Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⬆️ Upgrade Django to 4.2 #940

Closed
wants to merge 2 commits into from
Closed

⬆️ Upgrade Django to 4.2 #940

wants to merge 2 commits into from

Conversation

stevenbal
Copy link
Contributor

@stevenbal stevenbal marked this pull request as draft January 9, 2024 09:08
@codecov-commenter
Copy link

codecov-commenter commented Jan 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e2f4b64) 93.07% compared to head (9950ffc) 93.10%.
Report is 2 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #940      +/-   ##
===========================================
+ Coverage    93.07%   93.10%   +0.03%     
===========================================
  Files          828      828              
  Lines        28949    29116     +167     
===========================================
+ Hits         26943    27108     +165     
- Misses        2006     2008       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pi-sigma
Copy link
Contributor

pi-sigma commented Jan 9, 2024

Checklist to prepare the Django 4.2 LTS upgrade

3rd party packages to verify/make compatible

  • django-admin-index
  • django-axes
  • django-filer
  • django-hijack (not officially supported: link; upgrade to 3.04)
  • django-ordered-model (not officially supported, appears to work)
  • django-redis (not officially supported; upgrade to 5.4.0)
  • django-rosetta
  • django-sniplates (not officially supported; upgrade to 0.7.2)
  • django-treebeard (not officially supported; upgrade to 4.7)
  • maykin-django-two-factor-auth (incompatible, blocking)
  • django-localflavor (not officially supported; upgrade to 4.0 (breaking
    changes))
  • django-privates
  • django-cors-headers (not officially supported; upgrade to 4.3.1 (breaking changes))
  • django-autoslug
  • django-elasticsearch-dsl
  • django-import-export (not officially supported: link; upgrade)
  • django-solo
  • django-colorfield (upgrade to >=0.9.0)
  • django-registration (upgrade to 3.4)
  • django-view-breadcrumbs (upgrade to 2.5.1)
  • django_better_admin_arrayfield (not officially supported; seems to work, but see link)
  • django-timeline-logger (not officially supported; upgrade to 3.0.0 (breaking changes))
  • django-csp (not officially supported; seems to work)
  • django-csp-reports
  • mozilla-django-oidc-db (not officially supported; upgrade to 3.0.0 (breaking changes))
  • django-open-forms-client (not officially supported)
  • django-htmx (upgrade to 1.17.2)
  • django-yubin (not officially supported; upgrade to 2.0.2 (breaking changes))
  • django-image-cropping (not officially supported)
  • django-log-outgoing-requests

CMS-related packages

  • django-cms (not officially supported; upgrade to 4.1.0)
  • djangocms-text-ckeditor (upgrade to 5.1.5)
  • djangocms-link (not officially supported)
  • djangocms-file (not officially supported)
  • djangocms-picture (upgrade to 4.1.1)
  • aldryn-apphooks-config (upgrade to 0.7)

API packages

  • djangorestframework (upgrade to 3.14.0)
  • django-extra-fields (deprecated (link); replace with drf-extra-fields)
  • django-filter
  • drf-spectacular (upgrade to 0.27.0)
  • djangorestframework-camel-case

@pi-sigma
Copy link
Contributor

pi-sigma commented Jan 9, 2024

maykin-django-two-factor-auth seems to be the only package incompatible with the upgrade to 4.2. However, we have quite a few packages that don't officially support Django 4.2. Most of them can be upgraded (some with potentially breaking changes).

@pi-sigma pi-sigma force-pushed the feature/django-4.2 branch from 9b0c307 to 9950ffc Compare January 9, 2024 15:01
@alextreme
Copy link
Member

Superseded by #1024

@alextreme alextreme closed this Feb 13, 2024
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.

4 participants