Fix docs release builds running out of memory - #5960
Open
cloutiertyler wants to merge 1 commit into
Open
cloutiertyler wants to merge 1 commit into
cloutiertyler wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both docs release workflows abort during the Docusaurus build with
JavaScript heap out of memoryat roughly 2 GiB after running onspacetimedb-linux-small. The release toeddf9f501consequently updated the branch but did not upload the rebuilt docs or regenerate the LLM index.Move both docs jobs back to the existing
spacetimedb-linuxrunner 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:
git diff --checkpasses.NODE_OPTIONS=--max-old-space-size=8192passed and generated the static site.After merging, release docs by preserving the current
docs/releasetip with a tag, resetting it tomaster, and pushing. This keeps the workflow fix on the source branch rather than introducing release-only handwritten changes.