renovate[bot]
commented
6 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: example/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: example@1.0.0
npm error Found: @openedx/frontend-build@13.1.4
npm error node_modules/@openedx/frontend-build
npm error dev @openedx/frontend-build@"^13.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @openedx/frontend-build@">= 14.0.0" from @edx/frontend-platform@8.0.2
npm error node_modules/@edx/frontend-platform
npm error peer @edx/frontend-platform@"^7.0.0 || ^8.0.0" from @edx/frontend-component-header@5.3.1
npm error node_modules/@edx/frontend-component-header
npm error @edx/frontend-component-header@"5.3.1" 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-08T22_56_08_791Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T22_56_08_791Z-debug-0.log
File name: example-plugin-app/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: example-plugin-app@1.0.0
npm error Found: @openedx/frontend-build@13.1.4
npm error node_modules/@openedx/frontend-build
npm error @openedx/frontend-build@"^13.0.28" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @openedx/frontend-build@">= 14.0.0" from @edx/frontend-platform@8.0.2
npm error node_modules/@edx/frontend-platform
npm error peer @edx/frontend-platform@"^7.0.0 || ^8.0.0" from @edx/frontend-component-header@5.3.1
npm error node_modules/@edx/frontend-component-header
npm error @edx/frontend-component-header@"5.3.1" 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-08T22_56_16_770Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T22_56_16_770Z-debug-0.log
This PR contains the following updates:
5.3.1->5.3.2Release Notes
openedx/frontend-component-header (@edx/frontend-component-header)
### [`v5.3.2`](https://togithub.com/openedx/frontend-component-header/releases/tag/v5.3.2) [Compare Source](https://togithub.com/openedx/frontend-component-header/compare/v5.3.1...v5.3.2) ##### Bug Fixes - **deps:** update dependency [@fortawesome/react-fontawesome](https://togithub.com/fortawesome/react-fontawesome) to v0.2.1 ([d554de8](https://togithub.com/openedx/frontend-component-header/commit/d554de89ca364b89af3e31208737a361651829d4))Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.