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

Update dependency redux from v4.2.0 to v4.2.1 #218

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
redux (source) 4.2.0 -> 4.2.1 age adoption passing confidence

Release Notes

reduxjs/redux (redux)

v4.2.1

Compare Source

This bugfix release removes the isMinified internal check to fix a compat issue with Expo. That check has added in early 2016, soon after Redux 3.0 was released, at a time when it was still less common to use bundlers with proper production build settings. Today that check is irrelevant, so we've removed it.

What's Changed

Full Changelog: reduxjs/redux@v4.2.0...v4.2.1


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

Copy link
Contributor Author

renovate bot commented Nov 3, 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 could not resolve
npm ERR! 
npm ERR! While resolving: @material-ui/core@4.12.4
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"18.2.0" from the root project
npm ERR!   peer react@"^16.0.0 || ^17.0.0 || ^18.0.0" from @entur/auth-provider@1.1.0
npm ERR!   node_modules/@entur/auth-provider
npm ERR!     @entur/auth-provider@"1.1.0" from the root project
npm ERR!   9 more (@entur/micro-frontend, react-dropzone, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4
npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"4.12.4" from the root project
npm ERR!   peer @material-ui/core@"^4.0.0" from @material-ui/icons@4.11.3
npm ERR!   node_modules/@material-ui/icons
npm ERR!     @material-ui/icons@"4.11.3" from the root project
npm ERR!   1 more (@material-ui/lab)
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4
npm ERR!   node_modules/@material-ui/core
npm ERR!     @material-ui/core@"4.12.4" from the root project
npm ERR!     peer @material-ui/core@"^4.0.0" from @material-ui/icons@4.11.3
npm ERR!     node_modules/@material-ui/icons
npm ERR!       @material-ui/icons@"4.11.3" from the root project
npm ERR!     1 more (@material-ui/lab)
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-30T10_22_12_858Z-debug-0.log

@renovate renovate bot force-pushed the renovate/redux-4.x branch from bbe1ea2 to 72e7471 Compare November 3, 2023 08:44
@renovate renovate bot force-pushed the renovate/redux-4.x branch 5 times, most recently from a074e23 to 223ee24 Compare December 14, 2023 21:55
@renovate renovate bot force-pushed the renovate/redux-4.x branch from 223ee24 to 31419b0 Compare December 19, 2023 16:33
@renovate renovate bot force-pushed the renovate/redux-4.x branch from 31419b0 to e44a8ef Compare January 8, 2024 11:37
@renovate renovate bot force-pushed the renovate/redux-4.x branch from e44a8ef to b6b1789 Compare February 15, 2024 13:36
@renovate renovate bot force-pushed the renovate/redux-4.x branch 3 times, most recently from d90c504 to a25df10 Compare March 21, 2024 13:27
@renovate renovate bot force-pushed the renovate/redux-4.x branch from a25df10 to e934f39 Compare April 4, 2024 07:23
@renovate renovate bot force-pushed the renovate/redux-4.x branch 2 times, most recently from 33ed737 to 0745c00 Compare April 22, 2024 10:01
@renovate renovate bot force-pushed the renovate/redux-4.x branch 2 times, most recently from 60941d0 to efdc0c1 Compare April 30, 2024 10:22
@renovate renovate bot force-pushed the renovate/redux-4.x branch from efdc0c1 to e908e4e Compare August 2, 2024 13:36
Copy link
Contributor Author

renovate bot commented Aug 2, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @material-ui/core@4.12.4
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"18.2.0" from the root project
npm ERR!   peer react@"^16.0.0 || ^17.0.0 || ^18.0.0" from @entur/auth-provider@1.1.0
npm ERR!   node_modules/@entur/auth-provider
npm ERR!     @entur/auth-provider@"1.1.0" from the root project
npm ERR!   9 more (@entur/micro-frontend, react-dropzone, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4
npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"4.12.4" from the root project
npm ERR!   peer @material-ui/core@"^4.0.0" from @material-ui/icons@4.11.3
npm ERR!   node_modules/@material-ui/icons
npm ERR!     @material-ui/icons@"4.11.3" from the root project
npm ERR!   1 more (@material-ui/lab)
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4
npm ERR!   node_modules/@material-ui/core
npm ERR!     @material-ui/core@"4.12.4" from the root project
npm ERR!     peer @material-ui/core@"^4.0.0" from @material-ui/icons@4.11.3
npm ERR!     node_modules/@material-ui/icons
npm ERR!       @material-ui/icons@"4.11.3" from the root project
npm ERR!     1 more (@material-ui/lab)
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-12-17T15_58_57_156Z-debug-0.log

@renovate renovate bot force-pushed the renovate/redux-4.x branch from e908e4e to 3664f46 Compare August 19, 2024 17:58
@renovate renovate bot force-pushed the renovate/redux-4.x branch 3 times, most recently from 9bee90e to 1c3e4fa Compare December 16, 2024 13:20
@renovate renovate bot force-pushed the renovate/redux-4.x branch from 1c3e4fa to 154f953 Compare December 17, 2024 15:59
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