helmv3 manager doesn't detect dependencies with the tilde notation if an OCI registry is used

[leo-wr-ps]

What would you like help with?

I think I found a bug

How are you running Renovate?

Self-hosted

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

renovate-38.23.2 - On GitLab but can also reproduce locally

Please tell us more about your question or problem

Steps to Reproduce

Install renovate

mkdir /path/to/renovate
cd /path/to/renovate
npm install renovate

Create Helm Chart

mkdir /path/to/chart
cd /path/to/chart
helm create my-chart
cd my-chart

echo '{"$schema": "https://docs.renovatebot.com/renovate-schema.json", "enabledManagers": ["helmv3"]}' >> renovate.json5
git init  && git add . && git commit -m "Initial Commit"
export LOG_LEVEL=debug

Add a a new dependency in /path/to/chart/my-chart/Chart.yaml

dependencies:
  - name: argo-cd
    version:  ~6.6.8
    repository: oci://registry-1.docker.io/bitnamicharts

Run renovate

cd /path/to/chart/my-chart
npm exec --prefix /path/to/renovate -- renovate --platform=local

Notice from logs that

Dependency registry-1.docker.io/bitnamicharts/argo-cd has unsupported/unversioned value ~6.6.8

while a new version is detected if version 6.6.8 is specified

[github-actions[bot]]

Hi there,

Get your discussion fixed faster 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.

Good luck,

The Renovate team

[fad3t]

Also interested in this. Any way to work around this with some extra config in the meantime? Thx!

[fad3t]

From what I understand, the helmv3 manager supports both helm and docker as data sources. However only helm supports version ranges.

The following config block forces the helmv3 manager to use the helm versioning in any case:

  "packageRules": [
    {
      "matchManagers": ["helmv3"],
      "matchDatasources": ["docker"],
      "commitMessageTopic": "helm chart {{depName}}",
      "versioning": "helm"
    }
  ]

This worked for me.