[codex] Pin current turborepo and Bun dev versions#3002
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (10)
📝 WalkthroughWalkthroughA Changes
Poem
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 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)
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 |
🚀 Preview Deployment🔗 Preview Links
Preview updates automatically with new commits |
What changed
turbodevDependency to2.8.21.bun-versionfile with1.3.6.bun-versionviabun-version-filebun.lockso the pinned dependency state installs cleanly with--frozen!.bun-versionto.gitignoreso the Bun version file is tracked in this checkoutWhy
The repo was mixing multiple Bun versions across workflows (
1.3.2,1.3.3, and1.3.6) while the root package manager declaration already pointed atbun@1.3.6. Turbo was also still declared as a range inpackage.jsoneven though the lockfile had already resolved to2.8.21.Pinning both tools removes version drift between local development and CI and makes the intended toolchain explicit.
Impact
Validation
bun install --lockfile-onlybun install --frozen --ignore-scriptsSummary by cubic
Pin
turboto 2.8.21 and standardize on Bun 1.3.6 across local dev and CI by adding a.bun-versionfile and updating GitHub Actions to read it. This removes version drift and keeps frozen installs consistent.turbodevDependency to2.8.21..bun-versionwith1.3.6; workflows now usebun-version-fileinoven-sh/setup-bun@v2.bun.lockfor cleanbun install --frozeninstalls..gitignoreto ensure.bun-versionis committed.Written for commit 803119c. Summary will update on new commits.
Summary by CodeRabbit