Conversation
Recent Mend Renovate runs have been failing with kernel-out-of-memory shortly after the pnpm migration, using the full 3GB memory limit while processing lockfile updates. Renovate maintainers recommended starting with toolSettings.nodeMaxMemory set to 1024MB so pnpm keeps its own Node heap smaller and leaves headroom for the rest of the Renovate process on hosted runners. This is the first recommended mitigation from renovatebot/renovate #41972 / #40942 before asking Mend for more memory.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA new Possibly related issues
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #27350 +/- ##
==========================================
- Coverage 73.46% 73.45% -0.01%
==========================================
Files 1545 1545
Lines 123724 123724
Branches 14970 14967 -3
==========================================
- Hits 90897 90887 -10
- Misses 31827 31837 +10
Partials 1000 1000
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|



Summary
toolSettings.nodeMaxMemory: 1024to Ghost's Renovate configWhy this change
Recent Mend Renovate runs on Ghost have been failing with
kernel-out-of-memoryshortly after the pnpm migration, using the full 3GB memory limit while regeneratingpnpm-lock.yaml.In the failing runs, Renovate gets as far as:
Generating pnpm-lock.yaml for .Spawning pnpm install to create pnpm-lock.yamland then the job dies at
3.0GB (of 3.0GB limit)before it can return to branch updates or automerge logic.Renovate maintainers suggested starting with:
{ "toolSettings": { "nodeMaxMemory": 1024 } }as the first mitigation for pnpm OOMs on Mend-hosted infrastructure. The goal is to keep pnpm's own Node heap smaller so the overall Renovate process stays under the hosted runner memory ceiling.
Context
Notes
This does not solve every reason a given run may do no work — schedule and automerge eligibility still matter — but it should reduce the number of runs that fail before they even reach merge logic.