-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix(django): Upgrade to 6.0 #13842
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
base: dev
Are you sure you want to change the base?
fix(django): Upgrade to 6.0 #13842
Conversation
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
20382cc to
138543a
Compare
|
Waiting for django-commons/django-prometheus#489 |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Signed-off-by: kiblik <5609770+kiblik@users.noreply.github.com>
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
Although it's interesting to prepare for Django 6.0 compatibility, I think we should sit on this for a bit. Django 5.2 is an LTS release with a long support horizon, longer than 6.0. If we make it work for 6.0 but it breaks in 6.1 and we have to wait for some library to fix it we may get in trouble. TL;DR; Let's re-assess after the summer when 6.1 is available. |
TBD