OCI Helm feed - version picker lists image tags as chart versions; selection fails at acquisition due to multi-image manifest

[briggs-octo]

Severity

1 report

Version

2026.2.13190

Latest Version

None

What happened?

When an OCI repository hosts a Helm chart under plain SemVer tags (for example, 1.8.1) and the container image under v-prefixed tags (for example, v1.8.1) in the same repository, the version picker lists both tag families as versions of the same package, with no artifact-type distinction. A user can select a v-prefixed tag, which then fails at acquisition. The tag also has a v added to the already-v-prefixed tag, so the download reference becomes vv1.8.1.

Result:

• The picker lists both 1.8.1 (chart) and v1.8.1 (image index) as versions of the same package, with no artifact-type distinction.
• Selecting a v-tag succeeds at selection but fails later at acquisition: Invalid response when trying to download manifest from OCI registry (Unsupported OCI image manifest type: only single-image manifests are supported)
• The task log reads Downloading [package] vv1.8.1 - a v prepended to the already-v-prefixed tag.

Reproduction

1. Create an OCI Registry feed against a registry whose repository holds both the chart (tags like 1.8.1) and the container image (tags like v1.8.1).
2. Add a package reference to that repository and open the version picker.
3. Note that both tag families are listed as versions of the same package.
4. Select a v-prefixed tag (for example v1.8.1) and run a step that acquires the package.

Error and Stacktrace

Invalid response when trying to download manifest from OCI registry (Unsupported OCI image manifest type: only single-image manifests are supported)

More Information

No response

Workaround

Specify the non-v-prefixed version of the image tag when creating a release.