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 to the latest 3.2.14 security patch if you can; otherwise this is not usable anymore. #309

Closed
shaenr opened this issue May 20, 2022 · 3 comments
Closed

Upgrade Django to the latest 3.2.14 security patch if you can; otherwise this is not usable anymore. #309

shaenr opened this issue May 20, 2022 · 3 comments

Comments

@shaenr
Copy link

shaenr commented May 20, 2022

No description provided.

@shaenr shaenr changed the title Upgrade Django to the latest 3.2 security patch if you can; otherwise this is not usable anymore. Upgrade Django to the latest 3.2.14 security patch if you can; otherwise this is not usable anymore. May 20, 2022
@shaenr
Copy link
Author

shaenr commented May 20, 2022

I actually just realized I could get it to work with 2.2.13.... LTS :)

@WMRamadan
Copy link

Should probably keep requirements.txt at Django==3.2.*

@nitely
Copy link
Owner

nitely commented Apr 6, 2023

I just released v0.13 which supports django 3.2, and 4.2
remember to read the upgrade instructions if needed https://spirit.readthedocs.io/en/latest/upgrade.html

@nitely nitely closed this as completed Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@WMRamadan @nitely @shaenr