update next & react versions #5640
Conversation
🦋 Changeset detectedLatest commit: 5070e76 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Your org has enabled the Graphite merge queue for merging into mainAdd the label “merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
github-actions
bot
added
Dashboard
jnsdls
requested review from
a team,
MananTank,
gregfromstl,
jakubkrehel and
joaquim-verges
as code owners
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a typosquat?Package name is similar to other popular packages and may not be the package you want. Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
size-limit report 📦
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5640 +/- ##
==========================================
- Coverage 47.83% 47.82% -0.01%
==========================================
Files 1088 1088
Lines 56661 56661
Branches 4307 4305 -2
==========================================
- Hits 27104 27099 -5
- Misses 28859 28864 +5
Partials 698 698
*This pull request uses carry forward flags. Click here to find out more. |
jnsdls
force-pushed
the
12-05-update_next_react_versions
branch
from
bbfeed6 to
ee834bc
Compare
jnsdls
changed the base branch from
12-05-use_social_sdk_for_publisher_page
to
graphite-base/5640
Merge activity
|
closes: CNCT-2563 <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on updating various package dependencies to ensure compatibility with `react 19`, including the removal of release candidate versions and the addition of explicit peer dependencies. ### Detailed summary - Updated `@types/react` and `@types/react-dom` to version `19.0.0`. - Changed `next` version from `15.0.3` to `15.0.4`. - Updated `react` and `react-dom` to version `19.0.0`. - Incremented `@next/eslint-plugin-next` and `@next/mdx` to `15.0.4`. - Updated `shiki` to version `1.24.0` in multiple packages. > The following files were skipped due to too many changes: `pnpm-lock.yaml` > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
jnsdls
force-pushed
the
12-05-update_next_react_versions
branch
from
ee834bc to
679e333
Compare
closes: CNCT-2563 <!-- start pr-codex --> --- ## PR-Codex overview This PR updates various dependencies to ensure compatibility with `react 19`, including explicitly setting peer dependencies and updating package versions across multiple files. ### Detailed summary - Updated `@types/react` and `@types/react-dom` to `19.0.0`. - Changed `react` and `react-dom` versions to `19.0.0`. - Updated `next` versions from `15.0.3` to `15.0.4`. - Updated `shiki` versions from `1.22.2` to `1.24.0`. - Updated `@next/eslint-plugin-next` and `@next/mdx` versions to `15.0.4`. > The following files were skipped due to too many changes: `pnpm-lock.yaml` > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
jnsdls
force-pushed
the
12-05-update_next_react_versions
branch
from
679e333 to
5070e76
Compare
closes: CNCT-2563
PR-Codex overview
This PR updates various dependencies to ensure compatibility with
reactversion19.0.0, including changes to@types/reactand several package versions across the project.Detailed summary
@types/reactand@types/react-domto19.0.0.reactandreact-domversions to19.0.0across multiple packages.nextfrom15.0.3to15.0.4.shikiversion from1.22.2to1.24.0.@next/eslint-plugin-nextand@next/bundle-analyzerto15.0.4.