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
[FEAT] Support of Django 5 #375
base: master
Are you sure you want to change the base?
Conversation
@yangyubo @schinckel if you can please help review this? |
Does this require a new migration? |
Signed-off-by: Verdan <verdan@getselectstar.com>
It does require the migration, updated migration. |
Signed-off-by: Verdan <verdan@getselectstar.com> # Conflicts: # notifications/migrations/0009_alter_notification_options_and_more.py
Signed-off-by: Verdan <verdan@getselectstar.com>
@schinckel I have also incorporated the changes from branch v1.8 into this PR, to merge everything in the master branch. let me know if you think the otherwise. |
@schinckel @yangyubo any updates on this? |
@schinckel @yangyubo a gentle reminder to please help get this reviewed. |
name: Support of Django 5.x
about: Updates the models.py to support Django 5.x
title: "[FEAT] Support of Django 5.x"
labels: 'django, django5'
assignees: ''
Is your feature request related to a problem? Please describe.
We want to update the Django Version in our organization to support Django5. and the
index_together
is the only blocker from this package.Describe the solution you'd like
Update the indexes for the models
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This PR also incorporated the changes from branch v1.8, which were not in the master branch yet.