helm/codeapi Chart.yaml redis/minio dependencies break under FluxCD: Bitnami repo now resolves to oci://, unsupported protocol scheme

[meroo36]

helm/codeapi/Chart.yaml declares its redis and minio subchart dependencies against the legacy Bitnami HTTPS repo:

dependencies:
  - name: redis
    version: "24.1.0"
    repository: "https://charts.bitnami.com/bitnami"
    condition: redis.enabled
  - name: minio
    version: "17.0.21"
    repository: "https://charts.bitnami.com/bitnami"
    condition: minio.enabled

Bitnami has since migrated chart distribution to OCI-only (oci://registry-1.docker.io/bitnamicharts/...). The classic charts.bitnami.com/bitnami index still lists these chart versions, but the underlying download URL for them is now an oci:// reference. Any GitOps/CI tooling that resolves chart dependencies through the classic HTTP(S) Helm repository getter (e.g. FluxCD's source-controller, which builds HelmChart dependencies this way) can't follow that scheme, and dependency resolution fails outright.

Reproduction
Deploy this chart via a FluxCD HelmRelease/HelmChart (Git or Helm repository source), and observe:

$ kubectl get helmreleases.helm.toolkit.fluxcd.io
NAME               AGE   READY   STATUS
code-interpreter   50s   False   HelmChart 'code-interpreter/code-interpreter-code-interpreter' is not ready: dependency build error: failed to add remote dependency 'redis': chart download of version '24.1.0' failed: Get "oci://registry-1.docker.io/bitnamicharts/redis:24.1.0": unsupported protocol scheme "oci"

Since minio is pinned against the same broken repo, it will fail the same way once/if redis is worked around — this isn't a redis-only problem.

Environment
Chart: helm/codeapi (code-interpreter HelmRelease)
Deployed via FluxCD (helm.toolkit.fluxcd.io), HelmChart-based dependency build
Affected dependencies: redis (24.1.0), minio (17.0.21), both from https://charts.bitnami.com/bitnami