Error in Operator Release workflow: operator was not published on operatorhub.io after it merged about community-operators

[mvalarh]

@wallrj yes. it will be fixed in https://github.com/k8s-operatorhub/community-operators/actions/runs/1858645246

[mvalarh]

1. We are doing sync between index and git if there are some operator missing it is repairing them.
2. This is also strange for me, but since this version was not released longer time it might happen that older opm had bug.
   I am watching it now.

PS: These days i am recreating many operators in k8s, because we need to recreate bundles for many operators to show k8s max version we introduced recently

[mvalarh]

Fixed

[wallrj]

Ah, perhaps this will be fixed by:

• #782
• cd21785

But that begs the questions:

1. How come the previous operator got successfully deployed, only a few hours earlier, and other recent commits to master were also successfully deployed.
2. How come the pre-submit checks didn't prevent merging CSV with the missing "replaces" field during previous changes to the Couchbase CSV file.