Bug Report
What did you do?
Submitted PR #6401 for the scorecard-test-kuttl container image, which got merged and is part of the recent operator-sdk v1.29.0 release.
What did you expect to see?
After the operator-sdk v1.29.0 release, the image should be pushed to quay.io at https://quay.io/repository/operator-framework/scorecard-test-kuttl?tab=tags&tag=latest
What did you see instead? Under which circumstances?
The container image was not pushed to quay.io: https://quay.io/repository/operator-framework/scorecard-test-kuttl?tab=tags&tag=latest
Possible Solution
Additional context
The master tag gets updated, and there are versions tagged which are higher than the operator-sdk version. I think it'd make sense to sync the scorecard-test-kuttl versions with the operator-sdk versions to avoid confusion.
Bug Report
What did you do?
Submitted PR #6401 for the scorecard-test-kuttl container image, which got merged and is part of the recent operator-sdk v1.29.0 release.
What did you expect to see?
After the operator-sdk v1.29.0 release, the image should be pushed to quay.io at https://quay.io/repository/operator-framework/scorecard-test-kuttl?tab=tags&tag=latest
What did you see instead? Under which circumstances?
The container image was not pushed to quay.io: https://quay.io/repository/operator-framework/scorecard-test-kuttl?tab=tags&tag=latest
Possible Solution
Additional context
The master tag gets updated, and there are versions tagged which are higher than the operator-sdk version. I think it'd make sense to sync the scorecard-test-kuttl versions with the operator-sdk versions to avoid confusion.