release: v0.1.1236 - #3702
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 |
|
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 ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe release version changes from ChangesVersion synchronization
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This release updates the version consistently across the required generated and configuration files; no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
Closing as a duplicate of #3701, which was cut first (10:15Z vs 10:26Z). I checked before deferring rather than assuming: #3701 is correctly formed — exactly the 3 required files, all three agreeing on Worth stating clearly, because the branch histories differ but the released content does not: both #3697 and #3698 are already on No reason to prefer mine. Verification of the staging recovery continues against #3701. |
Release v0.1.1236
Ships the two fixes for the staging preview outage.
#3698 — bind the esbuild binary path outside project scope. esbuild resolves its binary once, when its module evaluates. The adapter imported it lazily, so that read landed inside a project env scope on the first transform, saw
undefined, and no esbuild service ever started — every TSX transform failed for the life of the process. Importing at startup binds the path while the host environment is still onprocess.env, with project env isolation untouched.#3697 — keep the failure that caused the ownership error. The ownership latch was created without a cause and
??=then discarded the real error, so every genuine esbuild failure surfaced as a lifecycle message. That masking is why the above took a day to find.Release hygiene
0.1.1236.deno.jsondiff is the version line only — the release script's unrelated reformatting of twodependenciesarrays was reverted.deno task generaterun and amended in; the script alone produced only 2 files.After merge
This does not complete the fix. Staging needs the release published, a server artifact rebuilt on it, and a deploy, before preview recovers. I'll verify against the deployed pods and logs rather than assuming the chain ran, then dispatch a staging Remote E2E Health run before merging veryfront-e2e#139.
Summary by CodeRabbit