mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-27 07:50:47 +00:00
Tyler Gillson
2e1a079c7f
Some charts define the image reference and its version as sibling keys
of the same object, with the parent key unrelated to the image name:
cli:
image: ghcr.io/fluxcd/flux-cli
tag: v2.7.2
The walker previously extracted the `image` string via
matchesHelmValuesInlineImage but, without an embedded version, produced
a version-less dependency that could never be updated; the sibling
`tag`/`version` key was invisible because
matchesHelmValuesDockerHeuristic requires the keys to live inside an
object whose parent key ends in `image`.
When an inline reference carries no version and no digest, adopt a
sibling `tag` (preferred) or `version` string as the version, reusing
the same update mechanics as the repository/tag object form
(replaceString = version, docker versioning, `{{newValue}}` template).
Inline references with an embedded version or digest keep current
behavior, and repository/tag objects never reach the inline branch.
Discussion #46265 documents the layout with a real-world example.
Signed-off-by: Tyler Gillson <tyler.gillson@gmail.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Renovate supports updating of Docker dependencies within Helm Chart values.yaml files or other YAML files that use the same format (via managerFilePatterns configuration).
Updates are performed if the files follow the conventional format used in most of the Helm charts:
image:
repository: 'some-docker/dependency'
tag: v1.0.0
registry: registry.example.com # optional key, will default to "docker.io"
image:
repository: 'some-docker/dependency'
version: v1.0.0
coreImage:
registry: docker.io
repository: bitnami/harbor-core
tag: 2.1.3-debian-10-r38
cli:
image: 'some-docker/dependency'
tag: v1.0.0
cli:
image: 'some-docker/dependency'
version: v1.0.0
If you need to change the versioning format, read the versioning documentation to learn more.