weibeu 8d44c6a1e8 fix: don't let ssh-keyscan abort SSH git clones (#4605) ...

cloneGitRepository runs `ssh-keyscan <host> >> known_hosts` as one step
of a `set -e` script. Hosts whose SSH endpoint waits for the client's
identification string first — Hugging Face's hf.co among them — never
complete the keyscan handshake, so it exits 1 and `set -e` aborts the
deploy before `git clone` ever runs.

Make ssh-keyscan non-fatal and let the real ssh client record the host
key on first connect (StrictHostKeyChecking=accept-new), which reaches
hosts ssh-keyscan can't scan. Same TOFU trust model, so no regression;
GitHub/GitLab/Gitea still pre-seed and verify known_hosts as before.

2026-06-30 16:13:40 -06:00

..

server

fix: don't let ssh-keyscan abort SSH git clones (#4605)

2026-06-30 16:13:40 -06:00