Bump from django 4.2.11 to 4.2.16

[SmithPeder]

I see now that this is actually a duplicate of #23 🙃 But, I would prefer to change the pyproject.yaml as well, as the >=3 semver is a bit broad. So, from the lockfile, we're running 4.2.11.

Fixes the 9 vulnerabilities here

• django  installed 4.2.11  affected <4.2.16  CVE CVE-2024-45230
• django  installed 4.2.11  affected <4.2.16  CVE CVE-2024-45231
• django  installed 4.2.11  affected <4.2.14  CVE CVE-2024-39614
• django  installed 4.2.11  affected <4.2.14  CVE CVE-2024-39330
• django  installed 4.2.11  affected <4.2.14  CVE CVE-2024-39329
• django  installed 4.2.11  affected <4.2.14  CVE CVE-2024-38875
• django  installed 4.2.11  affected <4.2.15  CVE CVE-2024-41991
• django  installed 4.2.11  affected <4.2.15  CVE CVE-2024-41990
• django  installed 4.2.11  affected <4.2.15  CVE CVE-2024-42005

Closes #23

[SmithPeder]

I am not sure how we normally merge stuff in the decorator, as there are many projects/teams that use it 🤔

[mortenkrane]

I am not sure how we normally merge stuff in the decorator, as there are many projects/teams that use it 🤔

Looks like you need to add a separate version bump commit like this: a670979, and then create a new release here: https://github.com/kolonialno/django-api-decorator/releases. From there the build, etc should be automatic.

[mortenkrane]

👍