Files
renovate/lib/modules/manager/hermit/readme.md
Will Pfleger 556b1be775 fix(manager/hermit): propagate git credentials to hermit install (#43524)
* fix(manager/hermit): propagate git credentials to hermit install

hermit install runs without git auth, failing silently for packages
hosted in private repos. Spread getGitEnvironmentVariables(['hermit'])
into extraEnv, matching the pattern used by cargo, gomod, poetry,
copier, vendir, and conan managers.

Passing ['hermit'] as additionalHostTypes ensures hostRules configured
with hostType: 'hermit' are picked up alongside the standard platform
host types.

Also guards against undefined stderr in the outer catch block —
non-UpdateHermitError exceptions rendered "undefined" in PR comments.

* test(manager/hermit): cover non-Error thrown value fallback

Exercise the String(err) branch in the generic error handler when
a non-Error value propagates from updateHermitPackage.

* fix: address review comments on hermit git auth

Remove unnecessary spread operator from getGitEnvironmentVariables() result
assignment and apply one-sentence-per-line docs convention.
2026-07-17 13:21:54 +00:00

754 B

Hermit package installation token

When upgrading private packages through, Hermit manager will uses one of the following two tokens to download private packages.

HERMIT_GITHUB_TOKEN
GITHUB_TOKEN

These environment variable could be passed on via setting it in customEnvironmentVariables.

Git credentials configured in hostRules are also automatically propagated to hermit install via GIT_CONFIG_* environment variables. This enables Hermit to fetch packages from private Git repositories without additional configuration.

Nested Hermit setup

Nested Hermit setup in a single repository is also supported. e.g.

├bin
├─hermit
├─(other files)
├
├nested
├─bin
├──hermit
├──(other files)