[!WARNING]
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
reduxjs/react-redux (react-redux)
### [`v7.2.9`](https://redirect.github.com/reduxjs/react-redux/releases/tag/v7.2.9)
[Compare Source](https://redirect.github.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://redirect.github.com/jspurlin) in [https://github.com/reduxjs/react-redux/pull/1952](https://redirect.github.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://redirect.github.com/reduxjs/react-redux/releases/tag/v7.2.8)
[Compare Source](https://redirect.github.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://redirect.github.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://redirect.github.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
### [`v7.2.7`](https://redirect.github.com/reduxjs/react-redux/releases/tag/v7.2.7)
[Compare Source](https://redirect.github.com/reduxjs/react-redux/compare/v7.2.6...v7.2.7)
This release updates React-Redux v7's peer dependencies to accept React 18 as a valid version, *only* to avoid installation errors caused by NPM's "install all the peer deps and error if they don't match" behavior.
**Note**: If you are now using React 18, **we strongly recommend using [the React-Redux v8 beta instead of v7.x!](https://redirect.github.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. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.
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 becomes conflicted, 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 contains the following updates:
7.2.6->7.2.9Release Notes
reduxjs/react-redux (react-redux)
### [`v7.2.9`](https://redirect.github.com/reduxjs/react-redux/releases/tag/v7.2.9) [Compare Source](https://redirect.github.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://redirect.github.com/jspurlin) in [https://github.com/reduxjs/react-redux/pull/1952](https://redirect.github.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://redirect.github.com/reduxjs/react-redux/releases/tag/v7.2.8) [Compare Source](https://redirect.github.com/reduxjs/react-redux/compare/v7.2.7...v7.2.8) This release fixes a bug in the 7.x branch that caused `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 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 was generated by Mend Renovate. View the repository job log.