release: v0.1.1236 - #3701
Conversation
📦 Client bundle boundary
A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 (2)
📝 WalkthroughWalkthroughThe package version and exported ChangesRelease version synchronization
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This release updates the project version and is merge-ready after normal checks and review; no actionable merge-blocking risk remains. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7841cef1d9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Release 0.1.1236.
Carries #3698 —
fix(bundler): bind the esbuild binary path outside project scope.Why now
Staging preview has returned 500 for every TSX transform since v0.1.1233.
Remote E2E Health / stagingfails deterministically onpreview-rendering.health.spec.tswithpreview returned 500. Verified on the staging renderer pod: zero esbuild processes running,ESBUILD_BINARY_PATHabsent from the process env, while the binary is present on disk at/tmp/veryfront-esbuild-0.28.1-*/esbuild. Extraction works; only the path binding was missing.The renderer image resolves
VERYFRONT_VERSIONfrom the latest non-draftveryfront/veryfrontrelease, so the fix cannot reach staging until this version is published.After merge
Remote E2E Healthwithtarget=staging.Summary by CodeRabbit