turbo

bf516e44 - fix: Prevent lockfile-aware yarn test from hanging on corepack downloads (#12095)

fix: Prevent lockfile-aware yarn test from hanging on corepack downloads (#12095) ## Summary - Adds `COREPACK_ENABLE_STRICT=0` to test helpers alongside the existing `COREPACK_ENABLE_DOWNLOAD_PROMPT=0`, preventing corepack from downloading exact package manager versions during tests - Widens `COREPACK_HOME` to `COREPACK_*` in `BUILTIN_PASS_THROUGH_ENV` so all corepack configuration vars pass through to tasks in strict env mode ## Context The previous fix (#12090) set `COREPACK_ENABLE_DOWNLOAD_PROMPT=0` on the turbo process to auto-approve corepack downloads. This prevents the stdin-prompt hang but still requires corepack to **download the exact version** from the network. On CI runners with slow or restricted network access, this download itself hangs — which is why `test_lockfile_aware_caching_yarn` was still hitting the >120s SLOW threshold. `COREPACK_ENABLE_STRICT=0` tells corepack to fall back to whatever package manager version is already installed rather than insisting on downloading the exact version from the `packageManager` field. Since these tests only need `echo building` to run, the exact yarn version is irrelevant. Additionally, `BUILTIN_PASS_THROUGH_ENV` only included `COREPACK_HOME`, meaning `COREPACK_ENABLE_DOWNLOAD_PROMPT` and `COREPACK_ENABLE_STRICT` were silently dropped from child task processes in strict env mode. Widening to `COREPACK_*` (consistent with `DOCKER_*`, `GITHUB_*`, `VERCEL_*`) ensures users who set these vars in their environment get them passed through to tasks.