Skip to content

chore(deps): lock file maintenance#4

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#4
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 19, 2023

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone Europe/Rome, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the renovate label Feb 19, 2023
@renovate renovate Bot requested review from DarkArtek and hikuch February 19, 2023 23:35
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from c1653d1 to 4b3cc4c Compare February 20, 2023 10:42
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 4b3cc4c to 10b7eb4 Compare March 15, 2023 12:53
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 10b7eb4 to 16ed8ef Compare March 24, 2023 17:23
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 16ed8ef to f856102 Compare April 28, 2023 01:02
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Aug 10, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @ahdcreative/react-components-ffxivita@0.3.2
npm ERR! Found: eslint@8.57.1
npm ERR! node_modules/eslint
npm ERR!   dev eslint@">=8.0.0" from the root project
npm ERR!   peer eslint@"^8.30.0" from @ahdcreative/eslint-config-ffxivita@1.0.2
npm ERR!   node_modules/@ahdcreative/eslint-config-ffxivita
npm ERR!     dev @ahdcreative/eslint-config-ffxivita@"^1.0.0" from the root project
npm ERR!   6 more (@typescript-eslint/eslint-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev eslint-config-xo@"latest" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@9.38.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=9.33.0" from eslint-config-xo@0.49.0
npm ERR!   node_modules/eslint-config-xo
npm ERR!     dev eslint-config-xo@"latest" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-10-22T00_51_07_402Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants