Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Update React version to v19 #7280

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pavinduLakshan
Copy link
Contributor

Purpose

$subject

Related Issues

  • N/A

Related PRs

  • N/A

Checklist

  • e2e cypress tests locally verified. (for internal contributers)
  • Manual test round performed and verified.
  • UX/UI review done on the final implementation.
  • Documentation provided. (Add links if there are any)
  • Relevant backend changes deployed and verified
  • Unit tests provided. (Add links if there are any)
  • Integration tests provided. (Add links if there are any)

Security checks

@pavinduLakshan pavinduLakshan marked this pull request as draft January 8, 2025 14:26
@wso2-jenkins-bot
Copy link
Contributor

⚠️ No Changeset found

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.

Refer Release Documentation to learn how to add a changeset.

@@ -118,12 +118,11 @@
"mustache": "^4.2.0",
"node-forge": "^0.10.0",
"rc-tree": "^4.0.0-beta.2",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react": "^19.0.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new update batching introduced with v18 caused some of the UIs in the Console to break (AFAIR, application protocols).

And we reverted to the legacy mode as a workaround: wso2/product-is#14912

Just FYI

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the info. However, we won't be able to upgrade to v19 anytime soon, as most of our dependencies are not yet ready to support v19. We may hopefully be able to figure out a solution for this by the time we are about to upgrade :)

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.

3 participants