Repository navigation
[ZEPPELIN-6738] Upgrade React to 19 and fix shared host integration - #5558
Open
voidmatcha wants to merge 14 commits into
Open
voidmatcha wants to merge 14 commits into
voidmatcha wants to merge 14 commits into
Conversation
This branch has not been deployed
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.
What is this PR for?
Upgrade the React remote to React 19 and fix shared integration behavior between the Angular host and React surfaces.
These changes were identified during the notebook Assistant frontend work and are separated from that feature so they can be merged without its server changes.
TicketService.handleAuthFailure, preserving logout guards. This prepares a shared entry point for later remote integrations; connecting Assistant requests is outside this PR.The callback, authentication and theme fixes do not inherently require React 19.
What type of PR is it?
Improvement
Todos
What is the Jira issue?
ZEPPELIN-6738
How should this be tested?
Production builds passed on the prerequisite branch. Chrome checks passed for repository form editing and cancellation, Select interaction, configuration table rendering and 18 rapid theme toggles, with no page errors.
Repository and configuration responses used browser-local fixtures because the QA repository list was empty. No server settings were saved.
Screenshots (if appropriate)
N/A
Questions: