Repository navigation
ci: pin Bun across web validation jobs - #13596
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: manaflow-ai/cmux/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe web CI workflow now pins Bun 1.3.14 in four jobs. A test verifies that every pinned Bun setup uses this version. ChangesBun version pinning
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to Web CI now consistently uses Bun 1.3.14 across its web jobs, reducing setup-time failures and remaining mergeable with normal checks. 🚥 Pre-merge checks | ✅ 24 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (24 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 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 |
|
This appears to be the repo-wide fix for the current burst of fake Web CI failures. I checked recent unrelated PR runs (#13591, #13598, #13587): Once the separate guard-ownership regression from #13585/#13535 is repaired on main, I'd prioritize getting this landed before interpreting Web failures on the other branches. |
6793d54 to
11df947
Compare
|
All contributors have signed the CLA ✍️ ✅ |
11df947 to
22562ea
Compare
Summary
Pin every
setup-buninvocation in the reusable web CI workflow to Bun 1.3.14.Four jobs already carried the explicit version. Four others relied on the action's default/latest resolution:
Why
Unversioned
setup-bunresolves release metadata through the GitHub API. Under a busy CI installation, two independent jobs in #13360 failed before running any project code because that tag lookup hit the installation rate limit.The workflow already standardizes its other Bun jobs on 1.3.14, so using the same explicit version everywhere removes that metadata lookup and makes the web lanes use one known toolchain.
Testing
Adds a workflow contract test requiring every
setup-bunblock inci-web.ymlto carrybun-version: "1.3.14".Demo Video
N/A — CI toolchain reliability only.
Checklist
Summary by cubic
Pins every
setup-buninvocation in the web CI workflow to Bun 1.3.14, preventing the jobs that relied on the action's default version from failing under GitHub API rate limits during heavy CI load. Adds a workflow contract test requiring everysetup-bunblock inci-web.ymlto specifybun-version: "1.3.14".Written for commit 22562ea. Summary will update on new commits.
Summary by CodeRabbit
Maintenance
Tests