$ opm alpha list bundles registry.stage.redhat.io/redhat/redhat-operator-index:v4.1(2-6) cluster-observability-operator
PACKAGE CHANNEL BUNDLE REPLACES SKIPS SKIP RANGE IMAGE
cluster-observability-operator development cluster-observability-operator.0.1.1 registry.stage.redhat.io/cluster-observability-operator/cluster-observability-operator-bundle@sha256:9462df4357c5a14224b26795dfdff6730fff0c7b59d3f21e66de42b27b7f4161
cluster-observability-operator development cluster-observability-operator.0.1.2 cluster-observability-operator.0.1.1 >=0.1.0 <0.1.2 registry.stage.redhat.io/cluster-observability-operator/cluster-observability-operator-bundle@sha256:64c6d96205ef04b9f48fed6ab9c7cabf03e429b5092a4d0fee47d7d350d451f2
cluster-observability-operator development cluster-observability-operator.0.1.3 cluster-observability-operator.0.1.2 >=0.1.0 <0.1.3 registry.stage.redhat.io/cluster-observability-operator/cluster-observability-operator-bundle@sha256:149cb521550a9459df6e47b6af576228227fb9d7bd8471fe887660d3a4dc8156
cluster-observability-operator development cluster-observability-operator.0.2.0 cluster-observability-operator.0.1.3 >=0.2.0 <0.2.0 registry.stage.redhat.io/cluster-observability-operator/cluster-observability-operator-bundle@sha256:51a82611a184122efad183774d0bfbb1502c171c34509ca72d64f6a8d2e69ec1
cluster-observability-operator development cluster-observability-operator.0.3.1 cluster-observability-operator.0.2.0 >=0.3.0 <0.3.1 registry.stage.redhat.io/cluster-observability-operator/cluster-observability-operator-bundle@sha256:9ffd4e4438b26e6f798f12551227bb1bfead552639bd50f3632ab3984692b335
Confirmed with OLM team: Though COO 0.2.0 doesn't support OCP 4.16 and 4.17, the definition COO0.3.0 replace COO0.2.0 has no issue