Publish packages 🚀#605
Merged
Merged
Conversation
kumar303
approved these changes
Apr 27, 2026
kumar303
left a comment
Contributor
There was a problem hiding this comment.
I'm not too familiar with the release process but the changelogs and everything else looks right 👍
Contributor
|
Thanks @kumar303 yeah I'm not either, who is? |
Member
seems like a permission thing. |
ffdb3c9 to
2278b96
Compare
2278b96 to
197942c
Compare
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
@remote-dom/[email protected]
Minor Changes
#604
7177edbThanks @justinhenricks! - FlushBatchingRemoteConnectionmutations on a microtask by defaultThe default
batchfunction used byBatchingRemoteConnectionnow schedules flushes on a microtask (viaqueueMicrotask, falling back toPromise.resolve().then(...)) instead of a macrotask viaMessageChannel/setTimeout.This ensures that DOM mutations made in the remote environment are delivered to the host before any
awaited RPC response resolves, avoiding a class of bugs where the host sees an RPC result before the element updates that produced it (for example, aperform()callback setting an error on a field, only to have the host run its post-awaitlogic before that error mutation arrives).If you were relying on the previous macrotask behavior, you can restore it by passing a custom
batchoption, e.g.:[email protected]
Patch Changes
7177edb]:[email protected]
Patch Changes
7177edb]:[email protected]
Patch Changes
7177edb]: