Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 22, 2023

This PR contains the following updates:

Package Change Age Confidence
@tsconfig/docusaurus (source) 1.0.6 -> 1.0.7 age confidence

Configuration

📅 Schedule: Branch creation - "after 9pm,before 6am" in timezone Africa/Johannesburg, 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.


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

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

@renovate
Copy link
Contributor Author

renovate bot commented Jun 22, 2023

⚠ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.4 || ^17.0.0" from @docusaurus/[email protected]
npm ERR! node_modules/@docusaurus/core
npm ERR!   @docusaurus/core@"^2.4.1" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-29T05_32_05_967Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-29T05_32_05_967Z-debug-0.log

@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch 2 times, most recently from 6b2a5ee to 9c96294 Compare July 18, 2023 09:00
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch 2 times, most recently from 362aa2f to dfbb99c Compare August 1, 2023 01:07
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from dfbb99c to ec2b530 Compare August 31, 2023 02:24
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from ec2b530 to bb4bb87 Compare November 17, 2023 05:46
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from bb4bb87 to 6896368 Compare January 8, 2024 05:04
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from 6896368 to 348fd11 Compare January 21, 2024 04:44
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from 348fd11 to 1ae0853 Compare February 2, 2024 05:57
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from 1ae0853 to 85091e1 Compare March 29, 2024 05:32
@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from 85091e1 to ca7da70 Compare January 25, 2025 03:38
Copy link
Contributor Author

renovate bot commented Jan 25, 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: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^18.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.4 || ^17.0.0" from @docusaurus/[email protected]
npm error node_modules/@docusaurus/core
npm error   @docusaurus/core@"^2.4.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 /runner/cache/others/npm/_logs/2025-08-23T03_31_42_291Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-23T03_31_42_291Z-debug-0.log

@renovate renovate bot force-pushed the renovate/tsconfig-docusaurus-1.x-lockfile branch from ca7da70 to d388a79 Compare August 13, 2025 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants