* refactor(datasource): separate registry URLs in cache keys with a colon Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io> Co-Authored-By: Claude Sonnet 5.5 <michael.kriese+claude-code@mend.io> * fix(datasource/go): separate the remaining cache key parts with a colon Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io> * refactor(datasource): build cache keys with a shared colon-joining helper Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io> * refactor: build all cache keys with buildCacheKey Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io> * refactor(http): keep GET package cache keys as the bare URL Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io> * refactor(cache): extend cache key helper to memory cache keys Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io> * refactor(datasource/go): prefix the goproxy cache keys with their purpose Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io> --------- Co-authored-by: Claude Opus 5.5 <michael.kriese+claude-code@mend.io>
This datasource reads index.yaml from a Helm chart repository.
Amazon S3 repositories
In addition to HTTP(S) repositories, an s3:// registry URL is supported, so charts hosted in an Amazon S3 bucket (or an S3-compatible backend) can be looked up:
dependencies:
- name: my-chart
version: 1.0.0
repository: s3://my-bucket/charts
Renovate then reads s3://my-bucket/charts/index.yaml with the AWS SDK, which signs the request with AWS Signature Version 4.
See Calling AWS Services from Renovate for how to configure your credentials.
For S3-compatible backends, set the self-hosted s3Endpoint and s3PathStyle configuration options.
You can also provide credentials specifically for a bucket with a hostRules entry.
Set hostType to helm, matchHost to the bucket name, username to the access key ID, password to the secret access key, and optionally token to the session token:
{
"hostRules": [
{
"hostType": "helm",
"matchHost": "my-bucket",
"username": "AKIAIOSFODNN7EXAMPLE",
"password": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
}
]
}
If no matching host rule provides both username and password, the default AWS credential provider chain is used.