Skip to content

[WIP] feat: prepare for gradio 6.28 compatibility - #127

Open
Col0ring wants to merge 2 commits into
mainfrom
feat/gradio-6.28
Open

Col0ring wants to merge 2 commits into
mainfrom
feat/gradio-6.28

Conversation

@Col0ring

Copy link
Copy Markdown
Collaborator

No description provided.

Gradio >= 6.9 mounts every custom component as its own Svelte root, which
broke context propagation across custom component boundaries. The fix landed
upstream in gradio 6.28 (gradio-app/gradio#13817), and it needs the vendored
preview runtime to expose `getAllContexts` so gradio can hand the ancestor
custom component context down to nested mounts.

- expose `getAllContexts` from the vendored preview svelte runtime entry
- require gradio >= 6.28.0 and bump @gradio/{client,statustracker,utils}
- omit `i18n_store` from the props forwarded to React components, the key in
  the omit list never matched the actual prop name
- ignore the iframeResizer sourcemap warning in `gradio cc dev` output

WIP: dependency version updates and the related user docs are not included
yet, they will follow in later commits.
@changeset-bot

changeset-bot Bot commented Sep 17, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: a0fefc4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant