fix(ci): pin Rollup to 4.62.4 - #398
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe workspace configuration now overrides ChangesRollup dependency pin
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This narrowly pins Rollup to 4.62.4 to stabilize CI dependency resolution, with the existing runtime and memory settings unchanged; no actionable merge-blocking risk remains after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 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 |
📦 Package Previewpnpm add https://pkg.pr.new/@opentiny/tiny-robot@6a30cac pnpm add https://pkg.pr.new/@opentiny/tiny-robot-kit@6a30cac pnpm add https://pkg.pr.new/@opentiny/tiny-robot-svgs@6a30cac commit: 6a30cac |
🧹 Preview Cleaned UpThe preview deployment has been removed. |

Summary
Why
CI currently runs
pnpm i --no-frozen-lockfile, whilepnpm-lock.yamlis ignored. A fresh install now resolves Rollup 4.63.0, so transitive dependencies can change without any repository diff.The recent upstream failure occurred after this dependency drift. In an A/B verification, changing only Rollup from the current 4.63.0 resolution to 4.62.4 made the complete workflow pass. Increasing the V8 heap to 8 GB and switching between Node 24 and Node 22 did not resolve the same failure.
Verification
--max-old-space-size=4096setting in 67.62 seconds.Follow-up
This override is intentionally temporary. The durable fix is to track
pnpm-lock.yamland use a frozen install in CI so transitive dependency updates are explicit and reproducible. PR #396 contains a broader lockfile-based approach.Summary by CodeRabbit