GitHub flipped the default runners from Node 20 → 24. With that, actions/setup-python@v5 using cache: pip crashes with Maximum call stack size exceeded during setup. The engine's test.yml already avoids this (it was switched to no pip cache).
Affected workflows (10) — all actions/setup-python@v5, Python 3.12
coverage-report.ymldeploy-pages.ymldump-refresh.ymlrefresh-data.ymltechapi-pr-validation-comment.ymltechapi-verify-comment.ymlverify-network.ymlverify-status.ymlweekly-ingest.ymlweekly-refresh.yml
Recommended fix
Remove the cache: pip line from each setup-python step (matching test.yml, which passes without it). validate-data.yml and test.yml are unaffected (no pip cache).
Found during a TechAPI-side repo cleanup pass.
GitHub flipped the default runners from Node 20 → 24. With that,
actions/setup-python@v5usingcache: pipcrashes withMaximum call stack size exceededduring setup. The engine'stest.ymlalready avoids this (it was switched to no pip cache).Affected workflows (10) — all
actions/setup-python@v5, Python 3.12coverage-report.ymldeploy-pages.ymldump-refresh.ymlrefresh-data.ymltechapi-pr-validation-comment.ymltechapi-verify-comment.ymlverify-network.ymlverify-status.ymlweekly-ingest.ymlweekly-refresh.ymlRecommended fix
Remove the
cache: pipline from eachsetup-pythonstep (matchingtest.yml, which passes without it).validate-data.ymlandtest.ymlare unaffected (no pip cache).Found during a TechAPI-side repo cleanup pass.