versions-renovate

Renovate skips version entries when the `# renovate:` annotation syntax is incorrect. The custom regex manager requires fixed key ordering, proper datasource selection, and exact regex placement to successfully parse and track your Kubernetes component versions.

To add an OCI Helm chart annotation, you must generate a `# renovate:` line with the correct datasource and depName keys. Differentiating between HTTP Helm charts and OCI Helm registries ensures Renovate selects the proper datasource for tracking.

Handle non-semver container image tags by applying `versioning=loose` in your Renovate annotation. This prevents parsing failures and ensures Renovate can still track and update image tags that do not follow standard semantic versioning rules.

Yes, Renovate supports tracking GitHub releases, GitHub tags, and Docker images in the same file. You must specify the correct datasource—github-releases, github-tags, or docker—in each annotation to ensure Renovate parses every entry correctly.

Fix Renovate annotation syntax by ensuring required keys like `datasource` and `depName` are present and ordered exactly as the custom regex manager expects. Validating against the expected key order prevents Renovate from ignoring your homelab version entries.

You need different Renovate datasources when tracking Helm charts from HTTP sources versus OCI registries. Selecting the correct helm or docker datasource ensures the annotation matches the registry type and allows Renovate to properly fetch chart updates.