Broken release pipe for KMM-hub (2.2.1)

[ybettan]

• PR to the repo was merged: operator kernel-module-management-hub (2.2.1) #5474
• Operator Release job failed: https://github.com/k8s-operatorhub/community-operators/actions/runs/12463931442
• The operator wasn't published in https://operatorhub.io/operator/kernel-module-management-hub (latest version is still 2.2.0)

---

/assign @mvalarh @J0zi
This issue is idle since last week and it is urgent.

[openshift-ci]

@ybettan: GitHub didn't allow me to assign the following users: J0zi.

Note that only k8s-operatorhub members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

• PR to the repo was merged: operator kernel-module-management-hub (2.2.1) #5474
• Operator Release job failed: https://github.com/k8s-operatorhub/community-operators/actions/runs/12463931442
• The operator wasn't published in https://operatorhub.io/operator/kernel-module-management-hub (latest version is still 2.2.0)

---

/assign @mvalarh @J0zi
This issue is idle since last week and it is urgent.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ybettan]

/cc @J0zi

[Allda]

@ybettan There was an issue with the operatorhub.io page and it wasn't properly redeployed. This PR (k8s-operatorhub/operatorhub.io#62) fixed it and the latest version reflects your changes. Please confirm.

[ybettan]

Thank you @Allda.

I do see the release in operatorhub.io indeed.
Closing the issue.