Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 31, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 17.0.84 -> 17.0.87 age adoption passing confidence

Configuration

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

@vercel
Copy link

vercel bot commented Mar 31, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
contentful ❌ Failed (Inspect) Jun 23, 2025 6:02am
contentful-staging ❌ Failed (Inspect) Jun 23, 2025 6:02am

@renovate renovate bot requested a review from a team as a code owner March 31, 2025 02:47
@renovate
Copy link
Contributor Author

renovate bot commented Mar 31, 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: @imgix/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^17.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0 || ^19.0.0" from @testing-library/[email protected]
npm error node_modules/@testing-library/react
npm error   dev @testing-library/react@"16.2.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 /runner/cache/others/npm/_logs/2025-06-23T06_02_08_868Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-23T06_02_08_868Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from b1269bb to 621debe Compare May 24, 2025 15:18
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/react to v17.0.85 chore(dev-deps): update dependency @types/react to v17.0.86 May 24, 2025
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 621debe to d9f80b7 Compare May 30, 2025 11:45
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/react to v17.0.86 chore(dev-deps): update dependency @types/react to v17.0.87 May 30, 2025
@renovate renovate bot enabled auto-merge (squash) June 23, 2025 06:02
@renovate renovate bot force-pushed the renovate/react-monorepo branch from d9f80b7 to 88bffc6 Compare June 23, 2025 06:02
@renovate renovate bot merged commit 9ad2c11 into main Jun 23, 2025
1 of 4 checks passed
@renovate renovate bot deleted the renovate/react-monorepo branch June 23, 2025 06:02
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.

1 participant