tests.yml's Build sibling packages and CSS step runs yarn cache clean at the repo root (line 464). The root package.json is "packageManager": "pnpm@11.8.0" since #440, so yarn 1.22.22 refuses:
error This project's package.json defines "packageManager": "yarn@pnpm@11.8.0".
However the current global version of Yarn is 1.22.22.
set -e fails the step, which fails the E2E Tests job, which trips the e2e_result == "failure" branch of the All Tests gate — so every run that executes E2E goes red.
Every other yarn invocation in the workflow sits inside a (cd platform/… ) subshell or a step with working-directory, all of which pin yarn@1.22.22. Line 464 is the only root-level one.
E2E is gated behind the run-e2e-tests label on PRs, so this only shows on push and workflow_dispatch. Master's push runs have been red since #440 landed — 32358923148, 32257662944, 32246225716 — and it also reddened the #442 verification dispatch 32359418036 where all four WAB shards passed.
Fix: run the clean from a yarn-pinned directory. Yarn 1's cache is global, so (cd platform/wab && yarn cache clean) clears the same cache the sibling installs filled. pnpm store prune would prune the wrong store — the disk pressure comes from the five yarn installs.
tests.yml'sBuild sibling packages and CSSstep runsyarn cache cleanat the repo root (line 464). The rootpackage.jsonis"packageManager": "pnpm@11.8.0"since #440, so yarn 1.22.22 refuses:set -efails the step, which fails theE2E Testsjob, which trips thee2e_result == "failure"branch of theAll Testsgate — so every run that executes E2E goes red.Every other yarn invocation in the workflow sits inside a
(cd platform/… )subshell or a step withworking-directory, all of which pinyarn@1.22.22. Line 464 is the only root-level one.E2E is gated behind the
run-e2e-testslabel on PRs, so this only shows onpushandworkflow_dispatch. Master's push runs have been red since #440 landed —32358923148,32257662944,32246225716— and it also reddened the #442 verification dispatch32359418036where all four WAB shards passed.Fix: run the clean from a yarn-pinned directory. Yarn 1's cache is global, so
(cd platform/wab && yarn cache clean)clears the same cache the sibling installs filled.pnpm store prunewould prune the wrong store — the disk pressure comes from the fiveyarn installs.