TanStack
OSS
ai
Sign in / Sign up
Open main menu
ai
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
fix/renovate-oom-lockfile-869
bdcf9b80 chore(renovate): fix lockfile-regen OOM blocking grouped dep PRs (#869) The single `group:allNonMajor` group updated every dependency in one PR, so Renovate's `renovate/artifacts` step regenerated the entire ~1.1MB lockfile across all workspace manifests in a single pnpm pass — with `pnpmDedupe` on top — and OOM'd on the heap limit (e.g. #719). The lockfile then never updated and every `--frozen-lockfile` check went red. - Drop `group:allNonMajor` in favor of smaller per-ecosystem groups (markdown/unified, ai provider sdks, build & test tooling, lint & format, framework ecosystems, @types, tailwind). A catch-all keeps the remainder bundled so we don't regress to one-PR-per-dep. Each PR now touches far fewer manifests, shrinking each lockfile pass. - Drop `pnpmDedupe` from postUpdateOptions — the full-lockfile dedupe pass was the main memory driver. - Add `minimumReleaseAge: "1 day"` to match pnpm's `minimumReleaseAge: 1440` (minutes) in pnpm-workspace.yaml, so Renovate doesn't propose versions pnpm will refuse to install. Note: raising the runner heap (NODE_OPTIONS=--max-old-space-size=8192) must be set in the Mend hosted env — it can't live in renovate.json. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Jack Herri...
J
Succeeded
fix/renovate-oom-lockfile-869
bdcf9b80 Merge 8b39305e8816cd262e3fa84d3a074fee867132e1 into 18809998fe705b669bacc0d7c60ff1fdafd60483
by Jack Herri...
J
Previous page
Previous
Next
Next page