renovate[bot]
commented
2 months ago ⚠ Artifact update problem
Renovate failed to update artifacts 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: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: frontend@0.1.0
npm error Found: date-fns@2.30.0
npm error node_modules/date-fns
npm error date-fns@"^2.29.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer date-fns@"^3.0.0" from date-fns-tz@3.1.3
npm error node_modules/date-fns-tz
npm error date-fns-tz@"^3.0.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-05-08T06_41_36_690Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T06_41_36_690Z-debug-0.log
File name: backend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: freerooms-backend@1.0.0
npm error Found: date-fns@2.30.0
npm error node_modules/date-fns
npm error date-fns@"^2.30.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer date-fns@"^3.0.0" from date-fns-tz@3.1.3
npm error node_modules/date-fns-tz
npm error date-fns-tz@"^3.0.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-05-08T06_41_43_171Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T06_41_43_171Z-debug-0.log
This PR contains the following updates:
^2.0.0->^3.0.0Release Notes
marnusw/date-fns-tz (date-fns-tz)
### [`v3.0.0`](https://togithub.com/marnusw/date-fns-tz/blob/HEAD/CHANGELOG.md#v300-6-April-2024) [Compare Source](https://togithub.com/marnusw/date-fns-tz/compare/v2.0.1...v3.0.0) - \[UPGRADE] Support `date-fns` v3 ([#265](https://togithub.com/marnusw/date-fns-tz/issues/265)) Thank you, [@christopherklint97](https://togithub.com/christopherklint97) - \[BUGFIX] Correct import of `date-fns@v3` format and use Babel Webpack loader for mjs files ([#271](https://togithub.com/marnusw/date-fns-tz/issues/271)) - \[BREAKING CHANGE] `date-fns` v2 is no longer supported - \[BREAKING CHANGE] Renamed `utcToZonedTime` to `toZonedTime` to make the name less confusing, just search & replace - \[BREAKING CHANGE] Renamed `zonedTimeToUtc` to `fromZonedTime` to make the name less confusing, just search & replace - \[BREAKING CHANGE] All functions are now exported using named exports, this requires changing direct imports from `import formatInTimeZone from 'date-fns-tz/formatInTimeZone'` to `import { formatInTimeZone } from 'date-fns-tz/formatInTimeZone'` - \[BREAKING CHANGE] Functions now don’t check the number of passed arguments, delegating this task to type checkers (This isn't fully implemented yet, but it should be the assumption moving forward, as it is in `date-fns`) - \[BREAKING CHANGE] Arguments are not explicitly converted to the target types. Instead, they are passed as is, delegating this task to type checkers (This isn't fully implemented yet, but it should be the assumption moving forward, as it is in `date-fns`) - \[BREAKING CHANGE] IE is no longer supported since `date-fns` no longer supports it - \[BREAKING CHANGE] Removed `flow` support since `date-fns` also removed itConfiguration
📅 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.