Version Packages#208
Merged
Merged
Conversation
d0049b5 to
a2e48f9
Compare
commit: |
teamchong
approved these changes
Jul 7, 2026
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
capnweb@0.10.0
Minor Changes
0b20ec6Thanks @ndisidore! - Add configurable receiver-side resource limits (RpcSessionOptions.limits) that cap bigint length, message nesting depth, and incoming message size to guard against untrusted-peer resource exhaustion (Deserializing untrustedbigintvalues can cause CPU exhaustion #184).Patch Changes
#190
6e5c562Thanks @taylorodell! - Several correctness and robustness fixes:Object.prototypemember.ERROR_TYPESnow has a null prototype, so a wire value such as["error","constructor",...]no longer resolves toObject(which produced aStringwrapper instead of anError, bypassinginstanceof Errorchecks), and a name like"toString"no longer resolves to a non-constructor and throws. Unknown names correctly fall back toError.Object.prototypekeys (andtoJSON) out of an error's own-property bag, matching the behavior already applied when deserializing plain objects. Keys such as__proto__,toString, andvalueOfare no longer copied onto deserialized errors.abortmessage handler now hands error handlers the unwrapped abort reason rather than the internal payload wrapper, matching therejecthandler.WebSocket.close().