Skip to content

Fix docs release builds running out of memory - #5960

Open
cloutiertyler wants to merge 1 commit into
masterfrom
codex/docs-build-memory
Open

cloutiertyler wants to merge 1 commit into
masterfrom
codex/docs-build-memory

Conversation

@cloutiertyler

Copy link
Copy Markdown
Contributor

Both docs release workflows abort during the Docusaurus build with JavaScript heap out of memory at roughly 2 GiB after running on spacetimedb-linux-small. The release to eddf9f501 consequently updated the branch but did not upload the rebuilt docs or regenerate the LLM index.

Move both docs jobs back to the existing spacetimedb-linux runner and give Node an explicit 8 GiB heap limit. The publish and LLM-generation jobs execute the same full Docusaurus build, so both need the change.

Failure evidence:

Validation:

  • Both workflow files parse as YAML; git diff --check passes.
  • Full local production docs build with NODE_OPTIONS=--max-old-space-size=8192 passed and generated the static site.

After merging, release docs by preserving the current docs/release tip with a tag, resetting it to master, and pushing. This keeps the workflow fix on the source branch rather than introducing release-only handwritten changes.

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.

1 participant