Renovate 43.129.1 breaks on my setup

[larsskj]

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

Gitea

Which version of Renovate are you using?

43.129.1

Please tell us more about your question or problem

I've been running Renovate for a long time as a Kubernetes cronjob and I have enabled auto-merge.

This has worked until now, but it broke early this morning - more precisely since the upgrade to 43.129.1. All repo scanning fails with a strange SSH error - even though I use HTTPS to access my Gitea server. Downgrading to 43.129.0 solves the problem.

I use the stock Renovate image renovate/renovate:43.129.0.

Configuration is basically done using environment variables from a Kubernetes secret. Everything is setup to use HTTPS, so I wonder why I get SSH errors? (See the log snippet below)

The error is logged over and over for each and every repo on the Gitea host.

Logs (if relevant)

Logs

Error: Use of "GIT_SSH_COMMAND" is not permitted without enabling allowUnsafeSshCommand at Object.action (file:///usr/local/renovate/node_modules/.pnpm/simple-git@3.36.0/node_modules/simple-git/src/lib/plugins/block-unsafe-operations-plugin.ts:15:22) at PluginStore.exec (file:///usr/local/renovate/node_modules/.pnpm/simple-git@3.36.0/node_modules/simple-git/src/lib/plugins/plugin-store.ts:54:29) at GitExecutorChain.attemptRemoteTask (file:///usr/local/renovate/node_modules/.pnpm/simple-git@3.36.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:84:34) at GitExecutorChain.attemptTask (file:///usr/local/renovate/node_modules/.pnpm/simple-git@3.36.0/node_modules/simple-git/src/lib/runners/git-executor-chain.ts:63:20)

[larsskj]

Hm - upgrading to 43.135.0 also solves the problem, but 43.129.1 still fails.

[jamietanna]

Yep, we reverted the package upgrade that caused it