Rodrigo

@auvipy: It turns out the changes were already committed to master, didn't see them, rebased and I fixed the blacken error so the CI passes

> I would say this is ready for review. Py3.12 is supported but Dj5 is not. Can you elaborate on why not? I think if the test suite passes it...

> If you can merge #9233 then Dj5 can be supported. If not, then this PR demonstrates that Py3.12 can be supported w/o Dj5. Indeed, in #9233: ``` py312-django42: OK...

I was going to merge all commits and add Tom and Auvipy to the co-authored in the log and it turns out it's another branch in the encode repo... :D...

https://github.com/encode/django-rest-framework/pull/9233 ?

These seem innocuous (no changes to the RN and small fixes) that won't hurt including: * https://github.com/encode/django-rest-framework/pull/9232 * https://github.com/encode/django-rest-framework/pull/9231 * https://github.com/encode/django-rest-framework/pull/9198 Other nice-to-haves that seem inobtrusive and sooner the better...

> I've noticed that 3.14.0 doesn't explicitly support Django 4.2. Can that be added to 3.15.0? Can you point out where? All I found is https://github.com/encode/django-rest-framework/pull/9233/commits/c77b0e92ce939087186584930279ad86c208e0e7 which already contains it

The title is misleading, I think "Provide support for disabling actions in viewsets by setting them to None" would be better (it's not a fix). Also, you should add to...

According to the [documentation](https://www.django-rest-framework.org/api-guide/viewsets/#custom-viewset-base-classes): > You may need to provide custom ViewSet classes that do not have the full set of ModelViewSet actions, or that customize the behavior in some...

You can use ```https://github.com/math-a3k/django-bootstrap-v5.git#egg=django-bootstrap-v5``` in the meantime