Skip to content

Conversation

@ribtoks
Copy link
Contributor

@ribtoks ribtoks commented Dec 26, 2025

This PR contains the following updates:

Package Change Age Confidence
eslint-config-next (source) 15.5.7 -> 15.5.9 age confidence
next (source) 15.4.10 -> 15.5.9 age confidence

Release Notes

vercel/next.js (eslint-config-next)

v15.5.9

Compare Source

Please see the Next.js Security Update for information about this security patch.

v15.5.8

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@ribtoks
Copy link
Contributor Author

ribtoks commented Dec 26, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: next-app@0.1.0
npm error Found: react@19.2.3
npm error node_modules/react
npm error   react@"^19.1.0" from next-app@0.1.0
npm error   packages/next-app
npm error     next-app@0.1.0
npm error     node_modules/next-app
npm error       workspace packages/next-app from the root project
npm error   peer react@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from next@15.5.9
npm error   node_modules/next
npm error     next@"15.5.9" from next-app@0.1.0
npm error     packages/next-app
npm error       next-app@0.1.0
npm error       node_modules/next-app
npm error         workspace packages/next-app from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.3.1" from react-dom@18.3.1
npm error node_modules/react-dom
npm error   react-dom@"^18.0.0" from next-app@0.1.0
npm error   packages/next-app
npm error     next-app@0.1.0
npm error     node_modules/next-app
npm error       workspace packages/next-app from the root project
npm error   peer react-dom@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from next@15.5.9
npm error   node_modules/next
npm error     next@"15.5.9" from next-app@0.1.0
npm error     packages/next-app
npm error       next-app@0.1.0
npm error       node_modules/next-app
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-12-26T02_12_29_240Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-12-26T02_12_29_240Z-debug-0.log

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