marksweb
commented
2 years ago Seems fair not moving to 2.0
Perhaps a 2.0 release might drop Django 3.0 (insecure version) and bring in 4.0.
Once cms has it, 4.0 and python 3.10 should be easy to add. I think the main 4.0 changes are to signals which the app doesn't (from what I've seen) have.
I was tempted to release this as 2.0.0 but as a major change with versioning has already happened in 1.0.0 we are already on a path of major changes being made.