Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): pin dependencies #24

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 22, 2023

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
@types/react (source) devDependencies pin ^18.0.28 -> 18.2.6 age adoption passing confidence
@types/react (source) devDependencies pin ^18.0.30 -> 18.2.6 age adoption passing confidence
@types/react-dom (source) devDependencies pin ^18.0.11 -> 18.2.4 age adoption passing confidence
react (source) dependencies minor 18.1.0 -> 18.3.1 age adoption passing confidence
react-dom (source) dependencies minor 18.1.0 -> 18.3.1 age adoption passing confidence

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)
facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 changed the title fix(deps): update react monorepo to v18.2.0 chore(deps): update react monorepo May 24, 2023
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 2991d2f to 5fee843 Compare May 26, 2023 15:49
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from 372be3c to 5e7c58a Compare June 19, 2023 14:41
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 3711250 to 8cd0126 Compare June 29, 2023 08:04
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from 4486e39 to 98cde1a Compare July 12, 2023 19:19
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from d0e394f to 37866ee Compare July 19, 2023 11:05
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from aa4b5bc to 19b3388 Compare July 27, 2023 20:20
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 191712c to b7d8e8a Compare August 1, 2023 15:29
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from bed5775 to b3f027a Compare August 9, 2023 23:29
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from debb605 to 49c9345 Compare August 22, 2023 20:40
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from c412132 to 2a19027 Compare September 19, 2023 11:33
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from 6ef24cc to 5f65358 Compare March 13, 2024 13:21
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from 07d7faa to 0e0c147 Compare March 20, 2024 13:38
@renovate renovate bot force-pushed the renovate/react-monorepo branch 7 times, most recently from 147a816 to 7d5316e Compare March 28, 2024 17:45
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from b1d0ec7 to 229ab33 Compare April 9, 2024 02:23
@renovate renovate bot force-pushed the renovate/react-monorepo branch 5 times, most recently from a000d5a to 458cc8a Compare April 15, 2024 23:19
Copy link
Contributor Author

renovate bot commented Apr 15, 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: example-react-native/package-lock.json
npm WARN ignoring workspace config at /tmp/renovate/repos/github/privy-open-source/pena-example/example-react-native/.npmrc 
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.3.1" from [email protected]
npm ERR!   example-react-native
npm ERR!     [email protected]
npm ERR!     node_modules/coba-react-native
npm ERR!       workspace example-react-native from the root project
npm ERR!   peer react@"*" from @privyid/[email protected]
npm ERR!   node_modules/@privyid/pena-react-native
npm ERR!     @privyid/pena-react-native@"^1.0.0" from [email protected]
npm ERR!     example-react-native
npm ERR!       [email protected]
npm ERR!       node_modules/coba-react-native
npm ERR!         workspace example-react-native from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"18.1.0" from [email protected]
npm ERR! node_modules/react-native
npm ERR!   react-native@"0.70.5" from [email protected]
npm ERR!   example-react-native
npm ERR!     [email protected]
npm ERR!     node_modules/coba-react-native
npm ERR!       workspace example-react-native from the root project
npm ERR!   peer react-native@"*" from @privyid/[email protected]
npm ERR!   node_modules/@privyid/pena-react-native
npm ERR!     @privyid/pena-react-native@"^1.0.0" from [email protected]
npm ERR!     example-react-native
npm ERR!       [email protected]
npm ERR!       node_modules/coba-react-native
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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

@renovate renovate bot force-pushed the renovate/react-monorepo branch from 458cc8a to 7a854a2 Compare April 17, 2024 11:22
@renovate renovate bot changed the title chore(deps): update react monorepo chore(deps): pin dependencies Apr 17, 2024
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from c6fc40c to 271bf0a Compare April 26, 2024 18:28
Copy link
Contributor Author

renovate bot commented Oct 10, 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: example-react-native/package-lock.json
npm WARN ignoring workspace config at /tmp/renovate/repos/github/privy-open-source/pena-example/example-react-native/.npmrc 
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.3.1" from [email protected]
npm ERR!   example-react-native
npm ERR!     [email protected]
npm ERR!     node_modules/coba-react-native
npm ERR!       workspace example-react-native from the root project
npm ERR!   peer react@"*" from @privyid/[email protected]
npm ERR!   node_modules/@privyid/pena-react-native
npm ERR!     @privyid/pena-react-native@"^1.0.0" from [email protected]
npm ERR!     example-react-native
npm ERR!       [email protected]
npm ERR!       node_modules/coba-react-native
npm ERR!         workspace example-react-native from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"18.1.0" from [email protected]
npm ERR! node_modules/react-native
npm ERR!   react-native@"0.70.5" from [email protected]
npm ERR!   example-react-native
npm ERR!     [email protected]
npm ERR!     node_modules/coba-react-native
npm ERR!       workspace example-react-native from the root project
npm ERR!   peer react-native@"*" from @privyid/[email protected]
npm ERR!   node_modules/@privyid/pena-react-native
npm ERR!     @privyid/pena-react-native@"^1.0.0" from [email protected]
npm ERR!     example-react-native
npm ERR!       [email protected]
npm ERR!       node_modules/coba-react-native
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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants