add changeset for channel reuse fix#31
Merged
Merged
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
1 participant
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.
Summary
#30 (allow reuse of channels) merged without a changeset, so the canary publish pipeline won't bump for it. This PR adds the missing changeset.
Same shape as #28 was for #22 -- single
.mdfile, nopre.jsonedit needed (changesets' tooling appends the entry on the nextversionrun).Description in the changeset
Patch bump for
@fltsci/taurpcdescribing the fix: previously the generated TS proxy mutated the originalChannel'sonmessagehandler in place when a transform layer was active, so passing the same channel to a second command re-wrapped it and double-decoded payloads. The proxy now wraps vianew Channel((response) => v.onmessage(transform(response)))instead of mutating the original.