It looks like the latest container images for these branches are not published correctly.
In main, the image was not published due to an error with the on_push CI (see here). This means that the latest change to the rockcraft project in dex did not created a charmedkubeflow/dex:2.39.1-bed284a image, which is inconsistent with the model we are following (having a tag per latest commit that changed the rockcraft project). To solve this we should re-run the build and publish CI from main. This is the same situation in the track branch.
Bug Description
It looks like the latest container images for these branches are not published correctly.
In
main
, the image was not published due to an error with theon_push
CI (see here). This means that the latest change to the rockcraft project index
did not created acharmedkubeflow/dex:2.39.1-bed284a
image, which is inconsistent with the model we are following (having a tag per latest commit that changed the rockcraft project). To solve this we should re-run the build and publish CI frommain
. This is the same situation in the track branch.To Reproduce
main
andtrack/3.0
Environment
No env
Relevant Log Output
Additional Context
No response