Release v0.1.1234 - #3687
Merged
Merged
Conversation
|
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 project version changes from ChangesRelease version update
Estimated code review effort: 1 (Trivial) | ~2 minutes Mergeability Score: ⚪ Minimal · up to This is a localized version bump with no actionable merge-blocking risk remaining beyond 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 |
This was referenced Aug 14, 2026
Merged
Closed
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the framework to
0.1.1234.This release exists because v0.1.1233 was cut before the fixes below landed.
mainand the published package have been sitting on the same version number whilemaincarried four commits the release did not, so none of this had reached a user.What this release carries
node_modulesis unmanaged. A globally installed CLI returned 500 on every request, including on a fresh scaffold.resolveAdapterread the adapter back out of an LRU with a non-null assertion.set()may insert and then evict an oversized value, soundefinedreachedgetConfigand threw on every request. Not runtime-specific — any oversized adapter, or eviction once the 50-entry cache fills, does it.lookupand relied onautoSelectFamily. Bun ≤ 1.3.13 honours neither, so the pin was inert there. It now dials the validated address directly and carries identity inHost+ SNI.main(deploy config exports, docs container recipe).Verification
A build containing all three fixes was run against every supported runtime, serving a real page rather than checking a boot log:
unprepared,adapter.fs,econnrefusedand process crashes all at zero across the four arms. Each fix was only observable once the others were present — the earlier defects masked the later ones — so they were verified in combination, not in isolation.Release commit
Exactly the three files the procedure expects, one line each:
The generated hydration runtime is byte-identical to the previous release once the version string is normalised (77774 bytes, delta 0), so no bundle drift rode along.
Two things the release script did that were undone: it reformatted unrelated
"dependencies"arrays indeno.json, and it created a localv0.1.1234tag. The reformatting is reverted so the diff is only the version bump, and the tag is deleted — CI creates the tag against the squashed merge.Summary by CodeRabbit
0.1.1234.