ci: ipyreact 0.6.1 in the integration locks - #1195
Merged
Merged
Conversation
0.6.1 invalidates the module registry when a replacement model is created, so the ES module hot reload test no longer depends on winning a race on loaded runners. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
maartenbreddels
temporarily deployed
to
ci/ipyreact-0.6.1 - solara-stable PR #1195
July 28, 2026 17:31 — with 
Render
Destroyed
Render
Destroyed
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.
Bumps
ipyreactfrom 0.6.0 to 0.6.1 in the four integration lock files.0.6.1 (widgetti/ipyreact#82) invalidates the page-global module registry when a replacement model is created. A hot reload replaces the per-kernel
Modulemodel rather than updating itscodetrait (an update on a closed widget never reaches the browser), so before 0.6.1 a consumer rendered alongside the replacement could resolve the previous module and keep rendering it — the update was lost permanently, not merely delayed.tests/integration/esm_test.py::test_ipyreact_module_hot_reloadtherefore depended on winning that race, which loaded runners lose.Verified: with 0.6.1 the test runs first-try green (both server flavors, no retries) in repeated CI runs, and in a 1-CPU container it goes from 2–3 of 3 runs stuck on the old version (150s budget exhausted) to 3/3 correct in ~6s.
Scheduled runs install unlocked and already pick up 0.6.1; this makes PR runs use it too.
🤖 Generated with Claude Code