chore: pin Bun 1.4.1 - #62
Conversation
|
|
Warning Review limit reachedNext included review available in 49 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request updates the pinned Bun version from 1.4.0 to 1.4.1 in the setup action and ChangesBun version alignment
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The tooling version pin is aligned across local package metadata and CI setup, with no remaining merge-readiness risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Summary
Pins Bun to 1.4.1:
packageManagerin the root, andbun-versionin the shared setup action. No lockfile changes;bun installon 1.4.1 resolves the committed lock byte-for-byte.1.4.1 is a patch release over 1.4.0: idle-memory reduction in JavaScriptCore, HTTP/2 for
Bun.serve, streamingBun.write, and a batch of bug fixes. Nothing we ship touches the changed APIs.Checklist
bun run checkpasses (build, format, lint, test, test:dom, typecheck, dedupe)Notes
Summary by CodeRabbit