Django 3.2 to 4.2 update ORACLE scheme changes 4.0

I just want confirmation that I am understanding this correctly:
[Django 4.0 release notes | Django documentation | Django](https://Table and column naming scheme changes on Oracle)

This issue and script only needs to be run on apps that already migrated to 4.0 (because the error is in 4.0 and has been fixed since?), and if I am updating directly from 3.2 to 4.2 I should not need it, is that correct?

Answering my own question: it is needed. it wasn’t exactly clear from the the documentation.
It would be nice if there was a migration that could be ran directly to fix it (with reverse migration too)