Repository navigation
Version Packages - #741
Merged
Merged
Version Packages#741
Conversation
kumar303
approved these changes
Oct 30, 2026
shopify-github-actions-access
Bot
force-pushed
the
changeset-release/remote-ui
branch
from
October 30, 2026 17:33
d6cea4a to
bef5e03
Compare
shopify-github-actions-access
Bot
force-pushed
the
changeset-release/remote-ui
branch
from
October 30, 2026 18:34
bef5e03 to
a888293
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 remote-ui, this PR will be updated.
Releases
@remote-ui/core@2.2.8
Patch Changes
#739
afb0c85Thanks @greatscotty! - Validate values received from the remote environment before storing or rendering them.createRemoteReceiver()now normalizes text node content to strings, rejects props containing objects that a UI framework would mistake for one of its own virtual nodes (Preact’sconstructor === undefinedshape, Vue’s__v_isVNodeflag), rejects__proto__as a prop name, and requires component types to be strings. The@remote-ui/reacthost renderer never passes remote-controlledchildren,ref,key,dangerouslySetInnerHTML,innerHTML, orouterHTMLprops to host components. The@remote-ui/vuehost renderer filters remote-controlled DOM content props,children,key,ref,__proto__, and allonVnode*lifecycle hooks. Vue hosts now require Vue>=3.5.9 <4.0.0, which checks the VNode flag before treating object children as virtual nodes. The validation helpers are exported from@remote-ui/corefor custom receivers.@remote-ui/dom@1.3.23
Patch Changes
afb0c85]:@remote-ui/htm@2.3.6
Patch Changes
afb0c85]:@remote-ui/react@5.0.9
Patch Changes
#739
afb0c85Thanks @greatscotty! - Validate values received from the remote environment before storing or rendering them.createRemoteReceiver()now normalizes text node content to strings, rejects props containing objects that a UI framework would mistake for one of its own virtual nodes (Preact’sconstructor === undefinedshape, Vue’s__v_isVNodeflag), rejects__proto__as a prop name, and requires component types to be strings. The@remote-ui/reacthost renderer never passes remote-controlledchildren,ref,key,dangerouslySetInnerHTML,innerHTML, orouterHTMLprops to host components. The@remote-ui/vuehost renderer filters remote-controlled DOM content props,children,key,ref,__proto__, and allonVnode*lifecycle hooks. Vue hosts now require Vue>=3.5.9 <4.0.0, which checks the VNode flag before treating object children as virtual nodes. The validation helpers are exported from@remote-ui/corefor custom receivers.Updated dependencies [
afb0c85]:@remote-ui/testing@1.4.7
Patch Changes
afb0c85]:@remote-ui/traversal@1.4.6
Patch Changes
afb0c85]:@remote-ui/vue@0.4.6
Patch Changes
#739
afb0c85Thanks @greatscotty! - Validate values received from the remote environment before storing or rendering them.createRemoteReceiver()now normalizes text node content to strings, rejects props containing objects that a UI framework would mistake for one of its own virtual nodes (Preact’sconstructor === undefinedshape, Vue’s__v_isVNodeflag), rejects__proto__as a prop name, and requires component types to be strings. The@remote-ui/reacthost renderer never passes remote-controlledchildren,ref,key,dangerouslySetInnerHTML,innerHTML, orouterHTMLprops to host components. The@remote-ui/vuehost renderer filters remote-controlled DOM content props,children,key,ref,__proto__, and allonVnode*lifecycle hooks. Vue hosts now require Vue>=3.5.9 <4.0.0, which checks the VNode flag before treating object children as virtual nodes. The validation helpers are exported from@remote-ui/corefor custom receivers.Updated dependencies [
afb0c85]: