Repository navigation
ci(frontend): unblock v0.113.0 web builds (heap cap) and fix release-tip styling - #6162
Conversation
The @agenta/oss Next build dies at the 4096 MB Node heap cap since the package extraction grew the build graph (PR #6152 CI shows the OOM; the build runners have 15.6 GB). Raise the cap to 8192 MB in the three gh Dockerfiles. Also run prettier on the two test files that fail the styling check on the release tip.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 4 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe Docker builder stages now allow 8192 MB of Node.js old-space memory. Two unit test files receive formatting-only updates with no behavior changes. ChangesBuilder memory configuration
Unit test formatting
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: 🔵 Low · up to The PR raises the web build memory cap and reformats two tests without changing product behavior. It is mergeable with explicit owner awareness that the required frontend lint check should be run for the touched web files. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The @agenta/oss build OOMs at the 4096 MB cap on this branch's package graph (both archs, two runs). Same change lands on release/v0.113.0 via #6162; identical lines merge clean.
Railway Preview Environment
Updated at 2026-08-21T15:59:19.016Z |
Context
Two CI reds on the v0.113.0 line, both introduced by the package-extraction merge (#6065) and its follow-up (#6152).
Changes
Dockerfile.ghfiles (oss, ee, mobile). The@agenta/ossNext build on [feat] /m catches up to the desktop: sign-in, chat turns, and Next 16 #6152 dies withFATAL ERROR: Reached heap limitat exactly the 4 GB cap, on both architectures, twice in a row (log). The build runners have 15.6 GB, so 8192 is safe. The ee Dockerfile gets the same bump because the staging deploy builds it from the same package graph.TypeScript formatcheck on the release tip itself (log):useAgentConversation.test.tsandEnhancedDrawerAntdProps.render.test.tsx. Formatting only, no code change.#6152 carries two more unformatted files of its own; those get a prettier commit on its head branch separately.
Tests
--checkpasses on both files after the write.