Skip to content

ci: fix Node 24 setup-python crash across 11 workflows - #45

Merged
Seungpyo1007 merged 1 commit into
mainfrom
fix/ci-node24-setup-python
Jul 15, 2026
Merged

ci: fix Node 24 setup-python crash across 11 workflows#45
Seungpyo1007 merged 1 commit into
mainfrom
fix/ci-node24-setup-python

Conversation

@Seungpyo1007

Copy link
Copy Markdown
Member

Problem

GitHub moved default runners to Node 24. actions/setup-python@v5 with cache: pip crashes at setup:

Run actions/setup-python@v5
Installed versions
Error: Maximum call stack size exceeded

This has been failing deploy-pages, verify-status, coverage-report, dump-refresh, refresh-data, weekly-ingest, weekly-refresh, verify-network, and both techapi-*-comment workflows on every run.

Fix

Apply the same fix test.yml already uses: bump actions/setup-python@v6 and remove cache: pip. (The @v6 bump alone does not stop the crash — removing the cache does; the bump additionally clears the Node 20 deprecation warning.)

  • 10 workflows: drop cache: pip, bump @v5@v6
  • validate-data.yml: @v5@v6 (had no cache; bumped for consistency)
  • techapi-pr-validation-comment.yml: also removed the now-orphaned cache-dependency-path + its comment

No behavior change beyond CI setup; pip installs still work (just uncached).

Fixes #44

GitHub's default runners moved to Node 24, where `actions/setup-python@v5`
with `cache: pip` crashes at setup with `Error: Maximum call stack size
exceeded`. This was breaking deploy-pages, verify-status, coverage-report,
the weekly jobs, and the techapi-* comment workflows.

Apply the same fix already used by test.yml: bump `actions/setup-python`
to `@v6` and remove `cache: pip` (bump alone does not fix the crash —
removing the cache does). Also drop the now-orphaned `cache-dependency-path`
in techapi-pr-validation-comment.yml.

Fixes #44
@Seungpyo1007
Seungpyo1007 merged commit 34331e3 into main Jul 15, 2026
1 check passed
@Seungpyo1007
Seungpyo1007 deleted the fix/ci-node24-setup-python branch July 15, 2026 01:56
Seungpyo1007 added a commit that referenced this pull request Jul 16, 2026
deploy-pages regenerates the full static dump (`python -m app.dump`) and
uploads it to GitHub Pages. Since the game category grew to ~962k records,
the artifact holds ~1M per-record files and the deploy step times out at
`Current status: syncing_files` / `Error: Timeout reached, aborting!`.

Mirror the TechAPI homepage workflow: after assembling `_site`, drop
`_site/v1/games` and remove `games` from `_site/v1/index.json`. Games stay
available as versioned data in the TechAPI repo; every other collection is
still published. This keeps the deploy within the Pages sync window.

(Latent since the ~1M import on 2026-07-12; only surfaced now that the
setup-python crash in #45 was fixed and the deploy step actually runs.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci: 10 workflows still use cache: pip — will break on GitHub's Node 24 runners

1 participant