Question regarding cluster rolling upgrade

I’m planning to upgrade a cluster in production using rolling upgrade. And it seems it is possible to upgrade all the way to the latest version with some intermediate steps. (say, 3.9.x to 3.12.x) Considering RabbitMQ and Erlang compatibility, it is unavoidable to upgrade Erlang version altogether.

Consulting with some relevant manuals, I found the following lines.

Seems it is recommended against to cluster nodes with different Erlang major versions.

RabbitMQ documentation says it is possible to rolling upgrade a cluster from 3.7.18 to the latest. (of course with some intermediate steps)

I feel like above two arguments are in conflict in some sense. When doing cluster rolling upgrades, nodes with different Erlang major version would coexist for some period of time.

So the question is, is it safe to rolling upgrade a cluster with Erlang major version change?

Thanks in advance.