mirror of
https://github.com/renovatebot/renovate.git
synced 2026-11-01 10:09:50 +00:00
Sebastian Poxhofer
9fc451c44d
Migrate pub, gleam, helmfile, pixi, mise, poetry, pep621/pdm and
pep621/uv onto `updateLockFile()`, so each manager keeps only its
command and `ExecOptions` construction.
Behaviour changes:
- Artifact error text now comes from `artifactErrorMessageFromExecError`,
i.e. a non-blank `err.stderr`, else a non-blank `err.stdout`, else
`err.message`. Previously pixi used `${err}` ("Error: " prefix), mise
joined stdout, stderr and message, and poetry rendered
"<stdout>\n<stderr>" (literally "undefined\nundefined" when the error
carried neither).
- helmfile, pixi, poetry, pdm and uv now return null instead of an
addition when the lock file is missing or empty after the run, which
is what gleam and mise already did.
- Unchanged/missing lock file debug messages are now uniformly
"<lockFileName> is unchanged" / "No <lockFileName> found". pub gains
such a message, mise loses "Returning updated mise lock file" and
poetry loses "Returning updated <lockFileName>".
Checks helmfile.yaml files and extracts dependencies for the helm datasource.
The helmfile manager defines this default registryAlias:
{
"registryAliases": {
"stable": "https://charts.helm.sh/stable"
}
}
If your Helm charts make use of repository aliases then you will need to configure an registryAliases object in your config to tell Renovate where to look for them. Be aware that alias values must be properly formatted URIs.
If you need to change the versioning format, read the versioning documentation to learn more.
Private repositories and registries
To use private sources of Helm charts, you must set the password and username you use to authenticate to the private source.
For this you use a custom hostRules array.
OCI registries
{
hostRules: [
{
// global login
matchHost: 'ghcr.io',
hostType: 'docker',
username: '<some-username>',
password: '<some-password>',
},
{
// login with encrypted password
matchHost: 'https://ghci.io',
hostType: 'docker',
username: '<some-username>',
encrypted: {
password: 'some-encrypted-password',
},
},
],
}