The skip range from the productized builds allows direct upgrade from 4.6 to 5.6 which has lead to several reported issues like: https://issues.redhat.com/browse/LOG-3836. Earlier version of logging moved responsibility of certs to the EO from CLO. Additionally there can be other migration paths which we need to require users to go through before getting to the "latest".

5.6.3 manifest

description: The Red Hat OpenShift Logging Operator for OCP provides a means for
configuring and managing your aggregated logging stack.
olm.skipRange: '>=4.6.0-0 <5.6.4'

description: The Red Hat OpenShift Logging Operator for OCP provides a means for
configuring and managing your aggregated logging stack.
olm.skipRange: '>=4.6.0-0 <5.6.4'

5.6 introduces replaces which will likely resolve future issues but the fix should likely to be to define the range for our N-2 policy similar to OCP. For example for 5.6 it should be: olm.skipRange: '>=5.4.0-0 <5.6.4'