Run details

aiWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/renovate-oom-lockfile-869
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

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>

nx run-many --targets=build --exclude=examples/**,testing/**

Succeeded

4 CPU cores

bdcf9b80872

100%

Cache hits

46 of 46 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

46 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

aiWorkspace