search

travi / hapi-react-router

hapi route to delegate routing for html content to react-router
MIT License
6 stars 2 forks source link

chore(deps): update dependency react-redux to v7.2.9 (master) #1231

Closed renovate[bot] closed 11 months ago

renovate[bot] commented 2 years ago

Mend Renovate logo banner

This PR contains the following updates:

Package Type Update Change OpenSSF
react-redux devDependencies patch 7.2.7 -> 7.2.9 OpenSSF Scorecard

Release Notes

reduxjs/react-redux (react-redux) ### [`v7.2.9`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.9) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.8...v7.2.9) This patch release updates the rarely-used `areStatesEqual` option for `connect` to now pass through `ownProps` for additional use in determining which pieces of state to compare if desired. The new signature is: ```ts { areStatesEqual?: ( nextState: State, prevState: State, nextOwnProps: TOwnProps, prevOwnProps: TOwnProps ) => boolean } ``` #### What's Changed - connect: pass ownProps to areStatesEqual by [@​jspurlin](https://togithub.com/jspurlin) in [https://github.com/reduxjs/react-redux/pull/1952](https://togithub.com/reduxjs/react-redux/pull/1952) **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v7.2.8...v7.2.9 ### [`v7.2.8`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.8) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.7...v7.2.8) This release fixes a bug in the 7.x branch that caused `` to unsubscribe and stop updating completely when used inside of React 18's ``. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of a `useLayoutEffect` instead of a `useMemo`. This was previously fixed as part of v8 development, and we've backported it. **Note**: If you are now using React 18, **we strongly recommend using [the React-Redux v8 beta instead of v7.x!](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.0-beta.3)**. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code. Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. Per [an update yesterday in the "v8 roadmap" thread](https://togithub.com/reduxjs/react-redux/issues/1740#issuecomment-1085190240), React-Redux v8 will be updated in the next couple days to ensure support for React 16.8+ as part of the next beta release. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version. **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v7.2.7...v7.2.8

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 2 years ago

⚠ 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:

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@0.20.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   dev react@"17.0.2" from the root project
npm ERR!   peer react@"17.0.2" from react-dom@17.0.2
npm ERR!   node_modules/react-dom
npm ERR!     dev react-dom@"17.0.2" from the root project
npm ERR!   1 more (react-redux)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.4.0 || ^16.0.0" from material-ui@0.20.2
npm ERR! node_modules/material-ui
npm ERR!   dev material-ui@"0.20.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^15.4.0 || ^16.0.0" from material-ui@0.20.2
npm ERR!   node_modules/material-ui
npm ERR!     dev material-ui@"0.20.2" 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! 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/2022-09-25T16_50_30_364Z-debug-0.log
codecov[bot] commented 2 years ago

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (125f9c6) compared to base (d63c6ba). Patch has no changes to coverable lines.

:exclamation: Current head 125f9c6 differs from pull request most recent head 2b4c7ee. Consider uploading reports for the commit 2b4c7ee to get more accurate results

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #1231 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 5 5 Lines 38 38 ========================================= Hits 38 38 ``` Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Matt+Travi). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Matt+Travi)

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.