build(deps): bump the react-stack group with 3 updates#89
Open
dependabot[bot] wants to merge 1 commit intomasterfrom
Open
build(deps): bump the react-stack group with 3 updates#89dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
dependabot
bot
added
the
dependencies
|
Deployment failed with the following error: Learn More: https://vercel.com/mediabubble?upgradeToPro=build-rate-limit |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
5 issues found across 9 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="apps/resident-portal/package.json">
<violation number="1" location="apps/resident-portal/package.json:23">
P1: Next 16.2.1 requires Node >=20.9.0, but the repo engine range still permits >=20.0.0. This can cause CI/dev runtime failures on allowed but unsupported Node versions.</violation>
<violation number="2" location="apps/resident-portal/package.json:27">
P2: React runtime was upgraded to 19.x, but TypeScript type packages remain on 18.x. Keep `@types/react` and `@types/react-dom` in the same major to avoid incorrect typings and TS friction.</violation>
</file>
<file name="apps/admin-dashboard/package.json">
<violation number="1" location="apps/admin-dashboard/package.json:35">
P1: `@types/react` and `@types/react-dom` in devDependencies are still on v18 while react/react-dom are bumped to v19. React 19 has breaking type changes (e.g., `useRef` requires an argument, implicit `children` removed from `FC`, ref callback cleanup). This will cause `typecheck` failures. Bump both type packages to `^19.0.0` to match.</violation>
</file>
<file name="apps/marketing/package.json">
<violation number="1" location="apps/marketing/package.json:25">
P2: Next 16.2.1 requires Node >=20.9.0, but the workspace engine range still allows unsupported Node 20.0–20.8.</violation>
<violation number="2" location="apps/marketing/package.json:25">
P1: Upgrading to Next 16 breaks the existing `next lint` script; linting will fail until the script is migrated.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| "jose": "4.15.9", | ||
| "lucide-react": "^0.344.0", | ||
| "next": "^15.5.14", | ||
| "next": "^16.2.1", |
There was a problem hiding this comment.
P1: Next 16.2.1 requires Node >=20.9.0, but the repo engine range still permits >=20.0.0. This can cause CI/dev runtime failures on allowed but unsupported Node versions.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/resident-portal/package.json, line 23:
<comment>Next 16.2.1 requires Node >=20.9.0, but the repo engine range still permits >=20.0.0. This can cause CI/dev runtime failures on allowed but unsupported Node versions.</comment>
<file context>
@@ -20,11 +20,11 @@
"jose": "4.15.9",
"lucide-react": "^0.344.0",
- "next": "^15.5.14",
+ "next": "^16.2.1",
"next-themes": "^0.4.6",
"qrcode": "^1.5.4",
</file context>
| "next-themes": "^0.4.6", | ||
| "react": "^18.3.1", | ||
| "react-dom": "^18.3.1", | ||
| "react": "^19.2.4", |
There was a problem hiding this comment.
P1: @types/react and @types/react-dom in devDependencies are still on v18 while react/react-dom are bumped to v19. React 19 has breaking type changes (e.g., useRef requires an argument, implicit children removed from FC, ref callback cleanup). This will cause typecheck failures. Bump both type packages to ^19.0.0 to match.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/admin-dashboard/package.json, line 35:
<comment>`@types/react` and `@types/react-dom` in devDependencies are still on v18 while react/react-dom are bumped to v19. React 19 has breaking type changes (e.g., `useRef` requires an argument, implicit `children` removed from `FC`, ref callback cleanup). This will cause `typecheck` failures. Bump both type packages to `^19.0.0` to match.</comment>
<file context>
@@ -30,10 +30,10 @@
"next-themes": "^0.4.6",
- "react": "^18.3.1",
- "react-dom": "^18.3.1",
+ "react": "^19.2.4",
+ "react-dom": "^19.2.4",
"react-i18next": "^14.1.3",
</file context>
| "lucide-react": "^0.344.0", | ||
| "negotiator": "^1.0.0", | ||
| "next": "^15.5.14", | ||
| "next": "^16.2.1", |
There was a problem hiding this comment.
P1: Upgrading to Next 16 breaks the existing next lint script; linting will fail until the script is migrated.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/marketing/package.json, line 25:
<comment>Upgrading to Next 16 breaks the existing `next lint` script; linting will fail until the script is migrated.</comment>
<file context>
@@ -22,7 +22,7 @@
"lucide-react": "^0.344.0",
"negotiator": "^1.0.0",
- "next": "^15.5.14",
+ "next": "^16.2.1",
"next-mdx-remote": "^6.0.0",
"next-themes": "^0.3.0",
</file context>
| "react": "^18.3.1", | ||
| "react-dom": "^18.3.1", | ||
| "react": "^19.2.4", | ||
| "react-dom": "^19.2.4", |
There was a problem hiding this comment.
P2: React runtime was upgraded to 19.x, but TypeScript type packages remain on 18.x. Keep @types/react and @types/react-dom in the same major to avoid incorrect typings and TS friction.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/resident-portal/package.json, line 27:
<comment>React runtime was upgraded to 19.x, but TypeScript type packages remain on 18.x. Keep `@types/react` and `@types/react-dom` in the same major to avoid incorrect typings and TS friction.</comment>
<file context>
@@ -20,11 +20,11 @@
- "react": "^18.3.1",
- "react-dom": "^18.3.1",
+ "react": "^19.2.4",
+ "react-dom": "^19.2.4",
"react-qr-code": "^2.0.18",
"sonner": "^1.7.4",
</file context>
| "lucide-react": "^0.344.0", | ||
| "negotiator": "^1.0.0", | ||
| "next": "^15.5.14", | ||
| "next": "^16.2.1", |
There was a problem hiding this comment.
P2: Next 16.2.1 requires Node >=20.9.0, but the workspace engine range still allows unsupported Node 20.0–20.8.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/marketing/package.json, line 25:
<comment>Next 16.2.1 requires Node >=20.9.0, but the workspace engine range still allows unsupported Node 20.0–20.8.</comment>
<file context>
@@ -22,7 +22,7 @@
"lucide-react": "^0.344.0",
"negotiator": "^1.0.0",
- "next": "^15.5.14",
+ "next": "^16.2.1",
"next-mdx-remote": "^6.0.0",
"next-themes": "^0.3.0",
</file context>
Bumps the react-stack group with 3 updates: [react](https://github.com/facebook/react/tree/HEAD/packages/react), [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) and [next](https://github.com/vercel/next.js). Updates `react` from 18.3.1 to 19.2.4 - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.4/packages/react) Updates `react-dom` from 18.3.1 to 19.2.4 - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.4/packages/react-dom) Updates `next` from 15.5.14 to 16.2.1 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v15.5.14...v16.2.1) --- updated-dependencies: - dependency-name: react dependency-version: 19.2.4 dependency-type: direct:production update-type: version-update:semver-major dependency-group: react-stack - dependency-name: react-dom dependency-version: 19.2.4 dependency-type: direct:production update-type: version-update:semver-major dependency-group: react-stack - dependency-name: next dependency-version: 16.2.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: react-stack ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/react-stack-9c659021d9
branch
from
adb247e to
f3b0c6f
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📦 Affected Packages
Diff: +3385 / -10245 lines
|
Lighthouse CI — Marketing Site
Core Web Vitals (Mobile)
|
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.
Bumps the react-stack group with 3 updates: react, react-dom and next.
Updates
reactfrom 18.3.1 to 19.2.4Release notes
Sourced from react's releases.
... (truncated)
Changelog
Sourced from react's changelog.
... (truncated)
Commits
90ab3f8Version 19.2.4612e371Version 19.2.3b910fc1Version 19.2.2053df4eVersion 19.2.15667a41Bump next prerelease version numbers (#34639)8bb7241Bump useEffectEvent to Canary (#34610)e3c9656Ensure Performance Track are Clamped and Don't overlap (#34509)68f00c9Release Activity in Canary (#34374)0e10ee9[Reconciler] Set ProfileMode for Host Root Fiber by default in dev (#34432)3bf8ab4Add missing Activity export to development mode (#34439)Updates
react-domfrom 18.3.1 to 19.2.4Release notes
Sourced from react-dom's releases.
... (truncated)
Changelog
Sourced from react-dom's changelog.
... (truncated)
Commits
90ab3f8Version 19.2.4612e371Version 19.2.3b910fc1Version 19.2.2053df4eVersion 19.2.18618113Bump scheduler version (#34671)1bd1f01Ship partial-prerendering APIs to Canary (#34633)2f0649a[Fizz] Removenonceoption from resume-and-prerender APIs (#34664)5667a41Bump next prerelease version numbers (#34639)e08f53bMatchreact-dom/statictest entrypoints and published entrypoints (#34599)8bb7241Bump useEffectEvent to Canary (#34610)Updates
nextfrom 15.5.14 to 16.2.1Release notes
Sourced from next's releases.
... (truncated)
Commits
ed7d2cev16.2.13e37bb4docs: post release amends (#91715)a15ec6edocs: fix broken Activity Patterns demo link in preserving UI state guide (#9...600cd2fFix adapter outputs for dynamic metadata routes (#91680)27886d3Turbopack: fix webpack loader runner layer (#91727)88fc430Fix server actions in standalone mode withcacheComponents(#91711)37aed86turbo-persistence: remove Unmergeable mmap advice (#91713)d6195ecFix layout segment optimization: move app-page imports to server-utility tran...6cb97d6Turbopack: lazy require metadata and handle TLA (#91705)e6b101a[turbopack] Respect{eval:true}in worker_threads constructors (#91666)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsSummary by cubic
Upgrade the React stack across the monorepo (web and mobile) to React 19 and Next 16 for new features, fixes, and consistent versions.
react: 18.3.1 → 19.2.4react-dom: 18.3.1 → 19.2.4next: 15.5.14 → 16.2.1Written for commit f3b0c6f. Summary will update on new commits.