fix(ci): resolve OOM in Algolia index workflow#17283
Merged
Conversation
The `next build` step was running out of memory on `ubuntu-latest` (7GB RAM), causing the runner to lose communication with the server. Three changes: 1. Cache `.next/cache` between runs (matches pattern from lint-404s.yml/test.yml) so incremental builds recompile only changed pages 2. Skip `generate-md-exports` which is unnecessary for Algolia indexing (the script only reads `.next/server/app/*.html`) 3. Set `NODE_OPTIONS=--max-old-space-size=6144` as a safety net for cold builds Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
chargome
approved these changes
Apr 9, 2026
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
2 participants
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.
DESCRIBE YOUR PR
The Algolia index workflow has been consistently OOM-ing when user docs change. The runner loses communication with the server during
next buildonubuntu-latest(7GB RAM).Root cause: This is the only workflow running
pnpm buildwithout.next/cachecaching —lint-404s.ymlandtest.ymlboth cache it and succeed on the same runner.Changes:
.next/cachebetween runs (matches existing pattern fromlint-404s.yml)generate-md-exports— unnecessary for Algolia (script only reads.next/server/app/*.html)NODE_OPTIONS=--max-old-space-size=6144as safety net for cold buildsIS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: