[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
If I got it right, the job failed the first time because the CRD chart was released successfully but the operator, who depends on the new release, could not get it because the repo is outdated. In the second execution, the repo is already updated (aware of the newly released CRD) and the operator release works successfully. Updating the repo before releasing it chart should fix the problem.
All Submissions:
closes #XXXXin your comment to auto-close the issue that your PR fixes (if such).If I got it right, the job failed the first time because the CRD chart was released successfully but the operator, who depends on the new release, could not get it because the repo is outdated. In the second execution, the repo is already updated (aware of the newly released CRD) and the operator release works successfully. Updating the repo before releasing it chart should fix the problem.