mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-19 17:11:42 -06:00
60f238c5af
GitHub-hosted images carry Node 24.19.0 in /opt/hostedtoolcache, so hosted jobs resolved from there and never populated the cached root. They still ran a restore that could only miss and then a save whose path did not exist, logging "Path Validation Error: Path(s) specified in the action for caching do(es) not exist" on every hosted job. No entry was ever written, so nothing was poisoned, but the warning is noise and the steps are pure waste on ~30 jobs per run. Gate both steps on runner.environment != 'github-hosted', the signal this workflow already uses for Blacksmith-only behavior, and gate the save on the setup step reporting that a download actually populated the root. That second guard also covers a future self-hosted image whose toolcache clears the floor. Verified on Blacksmith: a satisfying image toolcache leaves the root absent so the save is skipped, and a download populates it so the save runs.