renovate[bot]
commented
1 month ago ⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sentry/nextjs@7.120.0
npm error Found: next@15.0.3
npm error node_modules/next
npm error next@"15.0.3" from the root project
npm error peer next@"^13.5.0 || ^14.0.0 || ^15.0.0" from @storybook/nextjs@8.4.5
npm error node_modules/@storybook/nextjs
npm error dev @storybook/nextjs@"8.4.5" from the root project
npm error 2 more (next-joi, next-test-api-route-handler)
npm error
npm error Could not resolve dependency:
npm error peer next@"^10.0.8 || ^11.0 || ^12.0 || ^13.0 || ^14.0" from @sentry/nextjs@7.120.0
npm error node_modules/@sentry/nextjs
npm error @sentry/nextjs@"7.120.0" from the root project
npm error
npm error Conflicting peer dependency: next@14.2.18
npm error node_modules/next
npm error peer next@"^10.0.8 || ^11.0 || ^12.0 || ^13.0 || ^14.0" from @sentry/nextjs@7.120.0
npm error node_modules/@sentry/nextjs
npm error @sentry/nextjs@"7.120.0" from the root project
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/2024-11-26T09_18_07_515Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-26T09_18_07_515Z-debug-0.log
socket-security[bot]
This PR contains the following updates:
14.2.18->15.0.314.2.18->15.0.314.2.18->15.0.3Release Notes
vercel/next.js (@next/bundle-analyzer)
### [`v15.0.3`](https://redirect.github.com/vercel/next.js/releases/tag/v15.0.3) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.0.2...v15.0.3) ##### Core Changes - Read page name from work store in server module map proxy: [#71669](https://redirect.github.com/vercel/next.js/issues/71669) - codemod: should not transform when param is not used: [#71664](https://redirect.github.com/vercel/next.js/issues/71664) - \[dynamicIO] complete refactor to prerender: [#71687](https://redirect.github.com/vercel/next.js/issues/71687) - fix: metadata image route normalize path posix for windows: [#71673](https://redirect.github.com/vercel/next.js/issues/71673) - next-codemod(upgrade): optional catch when missing dev script: [#71598](https://redirect.github.com/vercel/next.js/issues/71598) - Avoid server action function indirection in Turbopack: [#71628](https://redirect.github.com/vercel/next.js/issues/71628) - fix: exclude `basePath` in `findSourceMapURL`: [#71719](https://redirect.github.com/vercel/next.js/issues/71719) - fix: stack frame text color in dark mode: [#71656](https://redirect.github.com/vercel/next.js/issues/71656) - Fix: revert the bad node binary handling: [#71723](https://redirect.github.com/vercel/next.js/issues/71723) - next-codemod: add empty `pnpm-workspace.yaml` to test fixtures to bypass PNPM workspace checks: [#71726](https://redirect.github.com/vercel/next.js/issues/71726) - warn on sync access if dynamicIO is not enabled: [#71696](https://redirect.github.com/vercel/next.js/issues/71696) - Update React from `69d4b800-20241021` to `45804af1-20241021`: [#71718](https://redirect.github.com/vercel/next.js/issues/71718) - next-upgrade: do not add `--turbopack` flag when `--turbo` exists in `next dev`: [#71730](https://redirect.github.com/vercel/next.js/issues/71730) - feat: stitch errors with react owner stack: [#70393](https://redirect.github.com/vercel/next.js/issues/70393) - \[dynamicIO] update data access error and documentation: [#71738](https://redirect.github.com/vercel/next.js/issues/71738) - Test cached form action with revalidate: [#71591](https://redirect.github.com/vercel/next.js/issues/71591) - Upgrade React from `45804af1-20241021` to `28668d39-20241023`: [#71745](https://redirect.github.com/vercel/next.js/issues/71745) - Fix race condition when setting client reference manifests: [#71741](https://redirect.github.com/vercel/next.js/issues/71741) - Fix fetch with no-store inside of use cache: [#71754](https://redirect.github.com/vercel/next.js/issues/71754) - Remove the bottom collapse button in dev overlay: [#71658](https://redirect.github.com/vercel/next.js/issues/71658) - \[dynamicIO] unify cache filling and lazy-module warming: [#71749](https://redirect.github.com/vercel/next.js/issues/71749) - Don't filter outConfiguration
📅 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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.