Version Packages - #249
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
August 20, 2026 13:24
9c53157 to
0266f44
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 20, 2026 14:57
0266f44 to
26a6f58
Compare
commit: |
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.12.0
Minor Changes
#253
46de5a7Thanks @ndisidore! - Fixed methods declared to returnPromise<RpcStub<T>>producing broken stub-of-stub result types; they now type the same asPromise<T>. If you annotated such a result asRpcPromise<RpcStub<T>>, writeRpcPromise<T>instead.#242
9751a4eThanks @ndisidore! -RpcPromisecan now be constructed from aPromise: pipelined calls queue in order until it settles, so you can publish a capability that doesn't exist yet.Patch Changes
#241
2de5871Thanks @ndisidore! - Fix RPC argument and capture leaks on failure paths: call arguments are now reliably disposed when a call is rejected, delivered to a broken or disposed stub, or fails to serialize.#251
7a6e5daThanks @ndisidore! - TheRpcPromiseconstructor now applies the same stub elision as method result types: wrapping aPromise<RpcStub<T>>produces the sameRpcPromise<T>a method declared to return that stub would, plain-interface stub payloads keep their stub type, and promises resolving to inline object literals with methods now infer correctly.#243
7e864a8Thanks @ndisidore! - Fix WritableStream stubs leaking call arguments when the stub was already disposed or the call path was invalid. All failure paths inWritableStreamStubHook.call()now dispose the copied arguments, matching ReadableStream behavior.capnweb-validate@0.3.0
Minor Changes
46de5a7Thanks @ndisidore! - Fixed methods declared to returnPromise<RpcStub<T>>producing broken stub-of-stub result types; they now type the same asPromise<T>. If you annotated such a result asRpcPromise<RpcStub<T>>, writeRpcPromise<T>instead.