Describe what should be investigated or refactored
The uds-package-gitlab renovate config is not working with registry1 image. I tested again after registry1 came back up so it is not related to that downtime.
This is currently causing misleading behavior where the renovate PR for gitlab package appears to be working (ci is passing with the old images), however the images for registry1 were not actually updated. Upstream image lookup is working fine
Links to any relevant code
You can see in the renovate PR only upstream packages are being identified and that ci is still passing which could have caused a messed up release.
Additional context
Off the top of my head, this appears to be an issue with the encrypted registry1 creds in the repo based on the debug logs, but its also possible that the renovate config needs account for tags with and without v (upstream images have v registryone images are just ).
Describe what should be investigated or refactored
The uds-package-gitlab renovate config is not working with registry1 image. I tested again after registry1 came back up so it is not related to that downtime.
This is currently causing misleading behavior where the renovate PR for gitlab package appears to be working (ci is passing with the old images), however the images for registry1 were not actually updated. Upstream image lookup is working fine
Links to any relevant code
You can see in the renovate PR only upstream packages are being identified and that ci is still passing which could have caused a messed up release.
Additional context
Off the top of my head, this appears to be an issue with the encrypted registry1 creds in the repo based on the debug logs, but its also possible that the renovate config needs account for tags with and without registryone images are just ).
v(upstream images have v