Configuring renovate to read helm dependencies

[SomniVertix]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitLab

Please tell us more about your question or problem

I am trying to configure the renovate bot to look at helm chart dependencies and notify if there's an update. An example Chart.yaml I have is:
`yaml
apiVersion: v1
name: wrapper
description: A Helm chart for Kubernetes
type: application
version: 0.1.0
appVersion: "1.0"

dependencies:

• name: argo-workflows
  version: 0.45.8
  repository: https://argoproj.github.io/argo-helm

https://github.com/argoproj/argo-helm/tree/main/charts/argo-workflows

`
I would like renovate to check if the argo-workflows helm chart has a version above 0.45.8.

My current renovate config is:
json { "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": [ "config:recommended", "github>renovatebot/.github" ], "platformAutomerge": true, "prCreation": "immediate", "packageRules": [ { "description": "Trigger breaking release for major updates", "matchPackageNames": [ "renovate/renovate", "ghcr.io/renovatebot/renovate" ], "matchUpdateTypes": [ "major" ], "commitMessagePrefix": "feat(deps)!:", "automergeType": "pr" }, { "description": "Trigger feature release for minor updates", "matchPackageNames": [ "renovate/renovate", "ghcr.io/renovatebot/renovate" ], "matchUpdateTypes": [ "minor" ], "semanticCommitType": "feat", "automergeType": "pr" }, { "description": "Trigger fix release for patch updates", "matchPackageNames": [ "renovate/renovate", "ghcr.io/renovatebot/renovate" ], "matchUpdateTypes": [ "patch", "digest" ], "semanticCommitType": "fix", "automergeType": "pr" }, { "description": "Schedule digest updates daily", "matchUpdateTypes": [ "digest" ], "extends": [ "schedule:daily" ] }, { "description": "Use node versioning and chore for node images", "matchPackageNames": [ "ghcr.io/containerbase/node" ], "semanticCommitType": "chore", "versioning": "node" }, { "description": "Update runner references in readme", "matchDepNames": [ "renovate-runner" ], "matchFileNames": [ "README.md" ], "additionalBranchPrefix": "docs-", "automerge": true, "dependencyDashboardApproval": false, "semanticCommitType": "docs", "separateMajorMinor": false } ], "customManagers": [ { "customType": "regex", "description": "Update docker references in gitlab variables", "managerFilePatterns": [ "/\\.gitlab-ci\\.yml$/" ], "matchStrings": [ "CI_RENOVATE_IMAGE[A-Z_]*\\s*:\\s*(?<depName>[^:]+?):(?<currentValue>[a-z0-9.-]+)(?:@(?<currentDigest>sha256:[a-f0-9]+))?" ], "datasourceTemplate": "docker", "versioningTemplate": "docker" }, { "customType": "regex", "description": "Update renovate-runner references", "managerFilePatterns": [ "/^README\\.md$/" ], "matchStrings": [ "\\s+- remote: https://gitlab\\.com/renovate-bot/renovate-runner/-/raw/(?<currentValue>v[0-9.]+)/", "\\s+ref: (?<currentValue>v[0-9.]+)\\s+", "\\s(?v[0-9.]+)\\s" ], "datasourceTemplate": "gitlab-releases", "depNameTemplate": "renovate-runner", "packageNameTemplate": "renovate-bot/renovate-runner", "versioningTemplate": "semver" } ], "gitlabci": { "managerFilePatterns": [ "/\\.gitlab-ci\\.yml$/" ], "pinDigests": true }, "helmv3": { "registryAliases": { "stable": "https://charts.helm.sh/stable" }, "commitMessageTopic": "helm chart {{depName}}", "managerFilePatterns": [ "/.*/Chart\\.ya?ml$/" ] }, "postUpdateOptions": ["helmUpdateSubChartArchives"] }

Any thoughts on how to do this?

Logs (if relevant)

Logs

 INFO: Dependency extraction complete (repository=cot/infrastructure/kac/poc-deployments, baseBranch=main)
       "stats": {
         "managers": {
           "gitlabci-include": {"fileCount": 1, "depCount": 1},
           "helm-values": {"fileCount": 7, "depCount": 8},
           "renovate-config-presets": {"fileCount": 1, "depCount": 1}
         },
         "total": {"fileCount": 9, "depCount": 10}
       }

[github-actions[bot]]

Hi there,

Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running Renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team