chore(deps): bump next from 14.2.35 to 15.5.10 in /dev-packages/e2e-tests/test-applications/create-next-app#19036
Conversation
Bumps [next](https://github.com/vercel/next.js) from 14.2.35 to 15.5.10. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.35...v15.5.10) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.10 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
This is a e2e test and should stay on this version |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
| "react": "18.2.0", | ||
| "react-dom": "18.2.0", | ||
| "typescript": "~5.0.0" |
There was a problem hiding this comment.
Bug: The create-next-app test application pins react and react-dom to 18.2.0 while upgrading to Next.js 15, which is inconsistent with other Next.js 15 test apps that use "latest".
Severity: MEDIUM
Suggested Fix
Update the package.json for the create-next-app test application. Change the versions of react and react-dom from 18.2.0 to "latest". Also, update @types/react and @types/react-dom to more recent versions to align with the dependency patterns of other Next.js 15 test applications in the repository.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: dev-packages/e2e-tests/test-applications/create-next-app/package.json#L20-L22
Potential issue: The `create-next-app` test application is being upgraded to Next.js
15.5.10 but retains pinned dependencies for `react` and `react-dom` at `18.2.0`, along
with outdated type definitions. This is inconsistent with other Next.js 15 test
applications in the repository, which use `"latest"` for React. This version mismatch is
likely to cause peer dependency errors during installation, potentially failing the CI
build. It also introduces a risk of runtime API incompatibilities between Next.js 15 and
the older React version, which could cause the E2E tests to fail.
Did we get this right? 👍 / 👎 to inform future reviews.
Bumps next from 14.2.35 to 15.5.10.
Release notes
Sourced from next's releases.
Commits
60a2aa9v15.5.10e5b834dfetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)39a2f6afeat(next/image)!: addimages.maximumResponseBodyconfig (#88183)bf9f084Sync DoS mitigations for React Flightc5de33ev15.5.9dd23399Backport facebook/react#35351 for 15.5.8 (#87086)7526cd6v15.5.81e9ec41Update React Version (#41)16141e5Update React Version (#30)e01e589Backport Next.js changes to v15.5.8 (#23)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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.