-
Notifications
You must be signed in to change notification settings - Fork 3
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
Django 3.2 #102
Comments
I have updated trix to django 3.2.16, and bumped all packages to the newest possible version while supporting python 3.6 -> 3.11. Made a 3.0.0b11 release of the changes. #107 was fixed as a side effect of upgrading markedown. I can't update to django 4 before cradmin-legacy gets support for it or we remove it from trix |
I think Django should be latest patch ( |
The Migrations when updating b10 => b11:
|
3.2.16 is the latest version but yes could change it to 3.2.*. or >=3.2.16, <4 to specify it a bit more. |
Created a new release b12 that contains some small fixes stemming from the django upgrade, there where some devtools that needed some strange fixes. And also contains fixes for the other issues in the milstone. |
@Levijatan: I believe this issue and the 3.0 milestone as a whole now is completed. 👍 |
The 3.0 Milestone is now merged into master and version 3.0.0 is released. |
No description provided.
The text was updated successfully, but these errors were encountered: