Bump react-redux from 7.2.6 to 8.1.1 in /desktop

[dependabot]

Bumps react-redux from 7.2.6 to 8.1.1.

Release notes

Sourced from react-redux's releases.

v8.1.1

This bugfix release tweaks the recent lazy context setup logic to ensure a single React context instance per React version, and removes the recently added RTK peerdep to fix an issue with Yarn workspaces.

Changelog

React Context Singletons

React Context has always relied on reference identity. If you have two different copies of React or a library in a page, that can cause multiple versions of a context instance to be created, leading to problems like the infamous "Could not find react-redux context" error.

In v8.1.0, we reworked the internals to lazily create our single ReactReduxContext instance to avoid issues in a React Server Components environment.

This release further tweaks that to stash a single context instance per React version found in the page, thus hopefully avoiding the "multiple copies of the same context" error in the future.

What's Changed

• fix: fix typescript error on non exported type by @​luzzif in reduxjs/react-redux#2034
• create singleton context by React version by @​phryneas in reduxjs/react-redux#2039
• remove RTK peerDep by @​markerikson in 44fc725

Full Changelog: reduxjs/react-redux@v8.1.0...v8.1.1

v8.1.0

This feature release adds new development-mode safety checks for common errors (like poorly-written selectors), adds a workaround to fix crash errors when React-Redux hooks are imported into React Server Component files, and updates our hooks API docs page with improved explanations and updated links.

Changelog

Development Mode Checks for useSelector

We've had a number of users tell us over time that it's common to accidentally write selectors that have bad behavior and cause performance issues. The most common causes of this are either selectors that unconditionally return a new reference (such as state => state.todos.map() without any memoization ), or selectors that actually return the entire root state ( state => state ).

We've updated useSelector to add safety checks in development mode that warn if these incorrect behaviors are detected:

• Selectors will be called twice with the same inputs, and useSelector will warn if the results are different references
• useSelector will warn if the selector result is actually the entire root state

By default, these checks only run once the first time useSelector is called. This should provide a good balance between detecting possible issues, and keeping development mode execution performant without adding many unnecessary extra selector calls.

If you want, you can configure this behavior globally by passing the enum flags directly to <Provider>, or on a per-useSelector basis by passing an options object as the second argument:

// Example: globally configure the root state "noop" check to run every time
<Provider store={store} noopCheck="always">
  {children}
</Provider>

// Example: configure `useSelector` to specifically run the reference checks differently:
function Component() {
  // Disable check entirely for this selector
</tr></table> 

... (truncated)

Commits

• e04515a Release 8.1.1
• 44fc725 Remove RTK peerDep
• 5c76414 Merge pull request #2039 from reduxjs/singletonContext-by-ReactVersion
• fafce9c create singleton context by React version
• 28f0aa2 fix: fix typescript error on non exported type (#2034)
• a222ceb Merge pull request #2037 from reduxjs/docs/switch-umami
• 3794848 Switch to Railway Umami instance
• 1e97aac Update action versions
• 117b397 Release 8.1.0
• fd26b3b Add release-it config file
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[github-actions]

Pull Request Test Coverage Report for Build 5392808875

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 51.436%

---

Totals
Change from base Build 5392783933:	0.0%
Covered Lines:	8242
Relevant Lines:	14873

---

💛 - Coveralls

[github-actions]

Pull Request Test Coverage Report for Build 5423183176

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 51.436%

---

Totals
Change from base Build 5423154065:	0.0%
Covered Lines:	8242
Relevant Lines:	14873

---

💛 - Coveralls

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.