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 Django from 4.1 to 4.2 (or 5.0!) 🔥 #162

Open
dawnwages opened this issue Dec 25, 2023 · 3 comments
Open

Upgrade Django from 4.1 to 4.2 (or 5.0!) 🔥 #162

dawnwages opened this issue Dec 25, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@dawnwages
Copy link
Collaborator

No description provided.

@dawnwages dawnwages added the enhancement New feature or request label Dec 25, 2023
@sarahboyce
Copy link
Member

Upgraded to Python 3.11: #317
Upgraded to Wagtail 5: #346

To upgrade to Django 5.0, Wagtail needs to be 5.2+ but we can upgrade to Django 4.2 already 👍

Will update the issue title to reflect work left to do.

@sarahboyce sarahboyce changed the title Upgrade Python 3.11, Django 5.0, Wagtail 5.0 Upgrade Django from 4.1 to 4.2 (or 5.0!) 🔥 Mar 30, 2024
@tim-schilling
Copy link
Member

I think puput is the blocker here.

@sarahboyce
Copy link
Member

I think puput is the blocker here.

Yes I think you're right
We need APSL/puput#286 to merge and a new release to be issued 👍
But I think Django 4.2 might already be possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tim-schilling @dawnwages @sarahboyce