Gradio 6.9.0 breaks things

[pablo-rerun]

Found this out when I was trying to update to 0.30.2

From Codex investigation

Gradio 6.9 Breakage Note

Summary

gradio-rerun 0.30.2 works with Gradio 6.8.x and below, but breaks on Gradio 6.9.0.

This is not a generic gradio-rerun / rerun-sdk mismatch. The breakage is caused by a Gradio frontend runtime change in 6.9.0.

Likely breakpoint

The relevant release change appears in Gradio 6.9.0:

• Release: gradio@6.9.0
• PR: #12879
• Title: Ensure svelte version mismatches do not break custom components

Links:

• https://github.com/gradio-app/gradio/releases/tag/gradio%406.9.0
• https://github.com/gradio-app/gradio/releases/tag/gradio%406.8.0
• Ensure svelte version mismatches do not break custom components gradio-app/gradio#12879

What changed

gradio-rerun 0.30.2 is a prebuilt Gradio custom component. Its generated frontend bundle imports Gradio-served Svelte runtime files such as:

• assets/svelte/svelte_internal_client.js
• assets/svelte/svelte_svelte.js
• assets/svelte/svelte_motion.js
• assets/svelte/svelte_transition.js
• assets/svelte/svelte_internal_flags_legacy.js

Those files exist in the Gradio wheels for:

• 6.6.0
• 6.7.0
• 6.8.0

Those files do not exist in the Gradio 6.9.0 wheel.

So gradio-rerun 0.30.2 is still targeting the pre-6.9 custom-component runtime layout.

Symptom

On gradio==6.9.0, the app starts, but the embedded Rerun viewer fails in-browser with missing frontend assets and does not initialize correctly.

Typical browser failures:

• 404 on svelte_runtime_entry.js
• 404 on /assets/svelte/svelte_internal_client.js
• 404 on /assets/svelte/svelte_svelte.js
• 404 on /assets/svelte/svelte_motion.js
• 404 on /assets/svelte/svelte_transition.js
• 404 on /assets/svelte/svelte_internal_flags_legacy.js

Verified behavior

Broken:

• gradio==6.9.0 + gradio-rerun==0.30.2 + rerun-sdk==0.30.2

Working:

• gradio==6.5.1 + gradio-rerun==0.30.2 + rerun-sdk==0.30.2
• gradio==6.8.0 minimal browser smoke test with gradio-rerun==0.30.2

Practical takeaway

The current workaround is to keep Gradio below 6.9.

The real fix is likely in gradio-rerun:

• rebuild the custom component against the post-6.9 Gradio custom-component runtime
• or otherwise update its frontend bundle so it no longer imports the removed pre-6.9 Svelte runtime files