feat!: Delete Django compatibility shims for <2.0

[browniebroke]

No description provided.

[browniebroke]

The url() function is deprecated and will be dropped in Django 4. This would be displayed while running test with warning enabled (-Wall)

[crccheck]

I need to do another pass to see if there are any other releases to do before doing a breaking change.

[browniebroke]

Side question: I noticed the title updates and now I'm wondering... Are you following conventional commit strictly?

Asking as I'm using it on some of my project and it streamline the release process massively, I basically automated changelog + release generation + upload to PyPI with python-semantic-release. It works great with GitHub actions, because unlike other CIs, you don't have to run it on each build to master, you make a workflow that is manually triggered with workflow_dispatch.

If you start using it for release, it's easy to forget, but there are actions to either lint the PR title or commits, depending on your merge strategy.

(sorry for the long disgression 😄)

[crccheck]

yes, I want to! In fact, I was hoping to put release automation in before the next breaking change. I've been using https://semantic-release.gitbook.io/semantic-release/ in NodeJS land and the tooling in JS land is pretty great. I'm not up to speed on the Python equivalent.

Thanks for the links! I've got another project where I run stuff manually on workflow_dispatch too and I kinda like it better than releasing every commit so far

[crccheck]

Django 4.0 is out! I'll try to push one last maintenance release using semantic-release then merge this