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.

Sign up for GitHub

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

Jump to bottom

Upgrade to Django 5.1 #17476

Closed
jeremystretch opened this issue Sep 12, 2024 · 1 comment
Closed

Upgrade to Django 5.1 #17476

jeremystretch opened this issue Sep 12, 2024 · 1 comment
Assignees
@arthanson
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Milestone
v4.2

Comments

@jeremystretch
Copy link
Member

Proposed Changes

Migrate from Django 5.0 to Django 5.1.

Justification

Django 5.1 was released in August 2024.
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user labels Sep 12, 2024
@jeremystretch jeremystretch added this to the v4.2 milestone Sep 12, 2024
@arthanson arthanson mentioned this issue Sep 26, 2024
Merged
@arthanson
Copy link
Collaborator

Ran into this issue: https://forum.djangoproject.com/t/non-editable-error-for-a-genericforeignkey-in-an-modelform-when-updating-to-version-5-1/35033

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

@arthanson arthanson

Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Projects
None yet
Milestone
v4.2
Development

No branches or pull requests
2 participants
@arthanson @jeremystretch