Skip to content

Conversation

@descope
Copy link
Contributor

@descope descope bot commented May 16, 2024

This PR contains the following updates:

Package Type Update Change
@types/react (source) dependencies minor 18.2.79 -> 18.3.3
@types/react-dom (source) dependencies minor 18.2.25 -> 18.3.0
react (source) dependencies patch 18.3.0 -> 18.3.1
react-dom (source) dependencies patch 18.3.0 -> 18.3.1

Release Notes

facebook/react (react)

v18.3.1

Compare Source

  • Export act from react f1338f

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.

@descope descope bot added the renovate label May 16, 2024
@descope
Copy link
Contributor Author

descope bot commented May 16, 2024

⚠ 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 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/eslint
npm error   dev eslint@"9.6.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.23.0 || ^8.0.0" from [email protected]
npm error node_modules/eslint-config-next
npm error   dev eslint-config-next@"14.2.4" 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-07-20T21_12_03_875Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-20T21_12_03_875Z-debug-0.log

@vercel
Copy link

vercel bot commented May 16, 2024

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

Name Status Preview Comments Updated (UTC)
nextjs-hackathon-template ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 20, 2024 9:13pm
nextjs-hackathon-template-demo-rishi ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 20, 2024 9:13pm

@descope descope bot force-pushed the renovate/react-monorepo branch from f1e391f to 6c05817 Compare May 24, 2024 22:50
@descope descope bot force-pushed the renovate/react-monorepo branch from 7b02b40 to 0fc6e76 Compare June 13, 2024 22:32
@descope descope bot force-pushed the renovate/react-monorepo branch from 0fc6e76 to e4e1033 Compare June 30, 2024 18:23
@descope descope bot force-pushed the renovate/react-monorepo branch from e4e1033 to 2ee9659 Compare July 20, 2024 21:12
@descope
Copy link
Contributor Author

descope bot commented Jul 29, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant