ForestryMC/IC2/TDLMPack do notactions/cache~/.gradle/caches. On Gitea they use setup-gradle with cache-provider: external (no Gradle-home Actions cache).
HMCL uniquely cached all of ~/.gradle/caches + wrapper → ~4GB restore, which killed Docker on the Windows act runner (npipe://./pipe/docker_engine).
Change
Wrapper-only cache (small). Same Gitea external pattern as the org.
## Why siblings were fine
ForestryMC/IC2/TDLMPack **do not** `actions/cache` `~/.gradle/caches`. On Gitea they use `setup-gradle` with `cache-provider: external` (no Gradle-home Actions cache).
HMCL uniquely cached all of `~/.gradle/caches` + wrapper → **~4GB** restore, which killed Docker on the Windows act runner (`npipe://./pipe/docker_engine`).
## Change
Wrapper-only cache (small). Same Gitea `external` pattern as the org.
Match ForestryMC/IC2: Gitea uses setup-gradle cache-provider external
with no whole-home actions/cache. Keep wrapper-only cache so restores
stay small on the Windows Docker runner.
layue13
merged commit 0d58eac860 into main2026-11-09 21:19:13 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why siblings were fine
ForestryMC/IC2/TDLMPack do not
actions/cache~/.gradle/caches. On Gitea they usesetup-gradlewithcache-provider: external(no Gradle-home Actions cache).HMCL uniquely cached all of
~/.gradle/caches+ wrapper → ~4GB restore, which killed Docker on the Windows act runner (npipe://./pipe/docker_engine).Change
Wrapper-only cache (small). Same Gitea
externalpattern as the org.