-
Notifications
You must be signed in to change notification settings - Fork 420
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
chore: setup dev:next-studio
to use react v19
#6685
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
No changes to documentation |
Component Testing Report Updated May 16, 2024 9:48 AM (UTC)
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/cac@6.7.14, npm/chalk@4.1.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems low stakes so ✅
Carolina is out so if you want to get someone else from DX to give a green we should reach out but otherwise 👍
Description
The easiest way to test React v19 without making any changes to our packages, peer deps and more, is to update
dev:next-studio
to use the latestcanary
ofnext
:What to review
This only affects
dev:next-studio
,dev:turbo-studio
and https://test-next-studio.sanity.build/test/structure deployments.Testing
If the vercel deployment for
test-next-studio
is green on this PR we're good to go 🙌Notes for release
N/A