Describe what should be investigated or refactored
We currently maintain a length and very specific renovate config for uds-core. UDS-Common maintains a great genericized config that we could adopt and help to extend if it doesn't catch all of our current dependencies. We will likely want to maintain our packagerules and maybe some other one-offs (neuvector image comes to mind), but the rest of these should be able to leverage the common config.
This should absolutely be validated to ensure we don't lose track of any dependencies.
Additional context
Worth noting that we are currently missing a check for one place zarf init is used in CI, which is covered by the common config - 1b5f604
Describe what should be investigated or refactored
We currently maintain a length and very specific renovate config for uds-core. UDS-Common maintains a great genericized config that we could adopt and help to extend if it doesn't catch all of our current dependencies. We will likely want to maintain our packagerules and maybe some other one-offs (neuvector image comes to mind), but the rest of these should be able to leverage the common config.
This should absolutely be validated to ensure we don't lose track of any dependencies.
Additional context
Worth noting that we are currently missing a check for one place zarf init is used in CI, which is covered by the common config - 1b5f604