chore(release): version packages - #19
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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
webactor@1.1.0
Minor Changes
#15
529f588Thanks @AStaroverov! - Report a lost message instead of dropping it silently.A message that a transport refuses now produces a
messageerrorenvelope carrying the transport's own error, so it stops being invisible. The report is routed to whoever was waiting for the message that failed: forward along its route when the envelope was already routed, such as a response or a channel handshake, and back along its checkpoints when it was still on its way out. Either way a pendingrequestrejects with the real cause instead of retrying until itsabortSignalfires. Transports implementing the platformmessageerrorevent now feed it into the same channel, so a failed deserialization reaches the endpoint as well.Keep it distinct from
error: anerrorenvelope still means the endpoint itself died and is what supervisors act on, whilemessageerrorsays one message was lost and the endpoint is fine.New public surface:
EnvelopeType.MessageError, theMessageErrorEnvelopetype, and theReasons.Undeliverable/Reasons.Undeserializablefallbacks.Also fixes a listener in an envelope emitter being able to swallow a whole dispatch: a throwing listener used to reject the internal dispatch promise as an unhandled rejection and skip every listener after it. It is now rethrown as an ordinary uncaught error, exactly like a throwing DOM event listener, and the remaining listeners still receive the envelope.