Environment Variable Handling

For Renovate

Renovate itself can be configured through a number of environment variables that correspond with global self-hosted configuration options, as well as some repository configuration options. These environment variables have the prefix with RENOVATE_.

Renovate also has some "experimental" variables that can be used with self-hosted deployments.

It is also possible to use the following configuration options to control Renovate's environment variables:

• processEnv: in a configuration file (i.e. config.js), allows specifying the values that Renovate will receive in its environment

With child processes

For security reasons, Renovate does not expose all environment variables to child processes. Instead, Renovate will use an allowlist of environment variables which it passes to any processes it calls.

This is an intentional decision to protect against two key attack vectors:

• an "insider attack" from a user of your self-hosted Renovate deployment
• an "outsider attack" from a malicious dependency

By limiting the environment variables provided to child processes, we can reduce the risk of a malicious actor from receiving access to potentially sensitive information, such as authentication tokens.

By default, Renovate will always pass the following environment variables to child processes:

• APPDATA
• CI
• COREPACK_DEFAULT_TO_LATEST
• COREPACK_ENABLE_NETWORK
• COREPACK_ENABLE_PROJECT_SPEC
• COREPACK_ENABLE_STRICT
• COREPACK_ENABLE_UNSAFE_CUSTOM_URLS
• COREPACK_HOME
• COREPACK_INTEGRITY_KEYS
• COREPACK_NPM_PASSWORD
• COREPACK_NPM_REGISTRY
• COREPACK_NPM_TOKEN
• COREPACK_NPM_USERNAME
• COREPACK_ROOT
• DOCKER_CERT_PATH
• DOCKER_HOST
• DOCKER_TLS_VERIFY
• GIT_SSL_CAINFO
• GIT_SSL_CAPATH
• HOME
• HTTP_PROXY
• http_proxy
• HTTPS_PROXY
• https_proxy
• LANG
• LC_ALL
• LOCALAPPDATA
• NO_PROXY
• no_proxy
• NODE_EXTRA_CA_CERTS
• PATH
• PATHEXT
• PNPM_MAX_WORKERS
• PNPM_WORKERS
• PROCESSOR_ARCHITECTURE
• PROGRAMFILES
• PROGRAMFILES(X86)
• SSL_CERT_DIR
• SSL_CERT_FILE

Note

Some managers pass additional environment variables where necessary.
For example, Renovate will convert Host Rules to the respective environment variables when calling npm, pnpm and yarn, including setting GIT_CONFIG_ environment variables.
This is not currently documented in full - you will need to review Renovate's code to see the full list.

As a self-hosted administrator, you can make it possible to specify other environment variables that repository owners can set, using:

• allowedEnv: allows users to specify values for allowlisted environment variables in their repository configuration using env
• customEnvVariables: administrator-defined environment variables, injected directly into every child process. Users cannot override these in their repository configuration
• exposeAllEnv: ⚠️ dangerously expose all environment variables from the Renovate process to all child processes
• extends: ["global:safeEnv"]: a curated list of commonly used environment variables that should be safe to allow users to configure with env. This is used by Mend-hosted Renovate

With these option(s) configured, users will be able to set these environment variable(s) in their repository configuration using env, as well as referencing them in any fields that support templating.

Using environment variables for secrets

Where possible, Renovate will try and redact secrets in its log messages, and the log output from any child processes. This relies on knowing whether the value is a secret for instance those configured through secrets or in hostRules.

If specifying an environment variable - through the above - with a value that isn't known to Renovate as a secret, this may lead to the secret being unknowingly exposed in the logs.

Precedence

When determining which environment variables Renovate should pass to a child process, Renovate merges with the following precedence order:

flowchart TD
    extraEnv["<strong><code>extraEnv</code></strong><br/><small>Manager-defined defaults/hints string value = default, null = inherit key only</small>"]
    parentEnv["<strong><code>parentEnv</code></strong><br/><small>process.env filtered to basicEnvVars<sup>1</sup> + string keys from extraEnv</small>"]
    globalConfigEnv["<strong><code>globalConfigEnv</code></strong><br/><small><code>customEnvVariables</code> set by self-hosted admin at startup</small>"]
    userConfiguredEnv["<strong><code>userConfiguredEnv</code></strong><br/><small><code>env</code> config in Renovate config file</small>"]
    forcedEnv["<strong><code>forcedEnv</code></strong><br/><small>Hardcoded per exec-call by Renovate internals</small>"]
    childProcess["<strong>Child Process</strong>"]
    exposeAllEnv["<strong><code>exposeAllEnv = true</code></strong><br/><small>Bypasses all layering, passes entire <code>process.env</code></small>"]
    processEnvConfig["<strong><code>processEnv</code></strong><br/><small></small>"]
    processEnv["<strong><code>process.env</code></strong><br/><small>The original process' <code>process.env</code> and <code>processEnv</code></small>"]
    allowedEnv["<strong><code>allowedEnv</code></strong><br/><small>Admin-controlled allowlist gates which environment variables repo owners may set</small>"]

    extraEnv -->|"overridden by"| parentEnv
    parentEnv -->|"overridden by"| globalConfigEnv
    globalConfigEnv -->|"overridden by"| userConfiguredEnv
    userConfiguredEnv -->|"overridden by"| forcedEnv
    forcedEnv --> childProcess

    exposeAllEnv -.->|"short-circuits to"| childProcess
    processEnvConfig -.->|"merged into"| processEnv
    processEnv -.->|"filtered with <code>basicEnvVars</code>"| parentEnv
    allowedEnv -.->|"restricts"| userConfiguredEnv

¹: the list of environment variables noted above that are always passed to child processes

Templating

Allowlisted environment variables can be referenced in templates. See templates and environment variables for more details.