[Snyk] Upgrade: , react-hook-form, react-query, redux, redux-thunk

[Erik-EFL]

Snyk has created this PR to upgrade multiple dependencies.

👯‍♂ The following dependencies are linked and will therefore be updated together.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Name	Versions	Released on

@redux-devtools/extension
from 3.2.3 to 3.3.0 | 4 versions ahead of your current version | 9 months ago
on 2023-12-08
react-hook-form
from 7.36.1 to 7.52.2 | 78 versions ahead of your current version | a month ago
on 2024-08-03
react-query
from 3.39.2 to 3.39.3 | 1 version ahead of your current version | 2 years ago
on 2023-01-25
redux
from 4.2.0 to 4.2.1 | 1 version ahead of your current version | 2 years ago
on 2023-01-28
redux-thunk
from 2.4.1 to 2.4.2 | 1 version ahead of your current version | 2 years ago
on 2022-11-04

Release notes

Package name: @redux-devtools/extension

• 3.3.0 - 2023-12-08
• 3.2.6 - 2023-11-04
• 3.2.5 - 2023-01-16
• 3.2.4 - 2023-01-09
  
  • Fix mocking Chrome API for Electron (#1748)
• 3.2.3 - 2022-08-11
  
  • Fix monitoring on opening panel (#1739)
  • Fix manifest.json for Edge (#1737)

from @redux-devtools/extension GitHub release notes

Package name: react-hook-form

• 7.52.2 - 2024-08-03
  

  👍 close #12108 useController should subscribe to exact field name of form's state (#12109)
  👍 chore: upgrade app deps
  🩻 fix: add useCallback for ref callback (#12078)
  🚀 fix: skip call executeBuiltInValidation if no sub-fields left (#12054)

  thanks to @ newsiberian, @ Wendystraite and @ abnud11

• 7.52.1 - 2024-07-02
  

  🐞 fix #12024 dirty not update issue with values prop (#12041)
  🐞 fix: field array validate rules shift errors (#12033)

  thanks to @ JardelCheung

• 7.52.0 - 2024-06-15
  

  ⚛️ close #11932 enable react 19 peer dependency (#11935)
  👮‍♀️ close #11954 getFieldState remove unnessaried inValidating and touched subscription (#11995)
  🐞 fix #11985 logic createFormControl check field before usage (#11986)
  ⌨️ fix: enforce type safety for deps property in RegisterOptions (#11969)
  🐞 fix #11922 keep dirty on reset with dirty fields (#11958)
  🚔 close #11937 add validation in the cleanup process in useController (#11938)
  Revert "⌨️ close: correct type of error field in getFieldState return object (#11831)"
  📖 fix: change info.values type in WatchObserver (#11917)

  thanks to @ nakaakist, @ IdoBouskila, @ pincy and @ peinguin

• 7.51.5 - 2024-05-21
  

  📖 fix broken link to examples in README.md (#11805)
  ⌨️ close: correct type of error field in getFieldState return object (#11831)
  🐞 fix #11842 radio buttons not disabled when multiple share a name (#11873)
  🐞 fix #11821 set value with disabled false before mount (#11880)
  🐞 fix setError to preserve existing errors elsewhere in the object (#11888)
  ⌨️ fix: add info.value type to WatchObserver (#11872)
  🫡 fix issue with internal set api (#11915)

  thanks to @ mjr2595 @ erashu212 @ SimonJTurner and @ peinguin

• 7.51.4 - 2024-05-04
  

  👹 close #11778 improve unregister omit key with getValues method (#11779)
  🐞 fix #11794 issue: Fields dirty state is not updated when passing values to useForm

• 7.51.3 - 2024-04-11
  

  🐞 fix #11773 regression on dirty check with reset (#11775)

• 7.51.2 - 2024-03-26
  

  🐞 fix #11719 validation stuck on true state (#11723)

• 7.51.1 - 2024-03-17
  

  🐛 bug(validatingFields, trigger): handle all fields validation trigger (#11624)
  💚 ci: cleanup actions versions (#11629)
  🐞 fix #11590 issue with trigger on validatingFields (#11613)

  thanks to @ Moshyfawn

• 7.51.0 - 2024-03-01
  

  💬 add isValidating and validatingFields to field state (#10657)

  const { formState: { validatingFields } } = useForm({ mode: 'onBlur' });

  ⌨️ chore: replace ts-ignore with ts-expect-error (#11573)
  🧗‍♂️ chore: update lib dev deps (#11548)
  💅 related #11541 improve dirty check when undefined provided with reset api
  😾 fix #11514 issue under strict mode reset invoke twice reset mounted field names with keepDirtyValues (#11546)
  🤡 fix flush root render hack (#11521)
  🧽 chore: removed unused utils and resp. test cases (#11476)
  🐞 close #11503 issue dirty field update with async validation (#11509)

  Revert "🔧 fix data param in handleSubmit when TTransformedValues is a union type (#11420)"
  Revert "✨ feat(values): priorities values over defaultvalues (#11399)" (#11545)

  ❤️ Thanks to @ deepgolani4, @ pbankonier and @ deepgolani4
  ❤️ Thank you principal.com for your contribution

• 7.50.1 - 2024-02-06
  

  🥲 Regression: Revert "⌨️ fix #10734 watch and useWatch without parameters return type (#11359)"

• 7.50.0 - 2024-02-01
• 7.49.3 - 2024-01-08
• 7.49.2 - 2023-12-13
• 7.49.1 - 2023-12-12
• 7.49.0 - 2023-12-09
• 7.48.2 - 2023-11-05
• 7.48.1 - 2023-11-04
• 7.48.0 - 2023-11-04
• 7.47.0 - 2023-10-02
• 7.46.2 - 2023-09-21
• 7.46.1 - 2023-09-04
• 7.46.0 - 2023-09-03
• 7.46.0-next.0 - 2023-08-13
• 7.45.4 - 2023-08-05
• 7.45.3 - 2023-08-04
• 7.45.2 - 2023-07-17
• 7.45.1 - 2023-06-28
• 7.45.0 - 2023-06-19
• 7.45.0-next.1 - 2023-06-18
• 7.45.0-next.0 - 2023-06-11
• 7.44.3 - 2023-06-01
• 7.44.3-beta.1 - 2023-05-31
• 7.44.3-beta.0 - 2023-05-31
• 7.44.2 - 2023-05-28
• 7.44.1 - 2023-05-27
• 7.44.0 - 2023-05-27
• 7.44.0-rc.5 - 2023-05-20
• 7.44.0-rc.4 - 2023-05-20
• 7.44.0-rc.3 - 2023-05-07
• 7.44.0-rc.1 - 2023-04-15
• 7.44.0-rc.0 - 2023-03-10
• 7.44.0-next.1 - 2023-02-16
• 7.44.0-next.0 - 2023-02-09
• 7.43.9 - 2023-03-30
• 7.43.8 - 2023-03-24
• 7.43.7 - 2023-03-18
• 7.43.6 - 2023-03-17
• 7.43.5 - 2023-03-06
• 7.43.4 - 2023-03-03
• 7.43.3 - 2023-03-01
• 7.43.2 - 2023-02-22
• 7.43.1 - 2023-02-07
• 7.43.0 - 2023-01-30
• 7.43.0-next.0 - 2023-01-18
• 7.42.1 - 2023-01-15
• 7.42.0 - 2023-01-13
• 7.42.0-next.0 - 2023-01-01
• 7.41.8-beta.0 - 2023-01-04
• 7.41.5 - 2023-01-04
• 7.41.4 - 2023-01-03
• 7.41.3 - 2022-12-30
• 7.41.2 - 2022-12-28
• 7.41.1 - 2022-12-23
• 7.41.0 - 2022-12-16
• 7.40.0 - 2022-11-29
• 7.40.0-next.1 - 2022-11-23
• 7.40.0-next.0 - 2022-11-17
• 7.39.7 - 2022-11-28
• 7.39.6 - 2022-11-27
• 7.39.5 - 2022-11-21
• 7.39.4 - 2022-11-14
• 7.39.3 - 2022-11-10
• 7.39.2 - 2022-11-09
• 7.39.1 - 2022-11-02
• 7.39.0 - 2022-11-01
• 7.38.0 - 2022-10-18
• 7.37.0 - 2022-10-06
• 7.37.0-next.0 - 2022-09-29
• 7.36.1 - 2022-09-23

from react-hook-form GitHub release notes

Package name: react-query

• 3.39.3 - 2023-01-25
• 3.39.2 - 2022-07-15

from react-query GitHub release notes

Package name: redux

• 4.2.1 - 2023-01-28
  

  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

  • Remove minified check by @ trajano in #4454

  Full Changelog: v4.2.0...v4.2.1

• 4.2.0 - 2022-04-18
  

  This release marks the original createStore API as @ deprecated to encourage users to migrate to Redux Toolkit, and adds a new legacy_createStore API as an alias without the deprecation warning.

  Goal

  Redux Toolkit (the @ reduxjs/toolkit package) is the right way for Redux users to write Redux code today:

  https://redux.js.org/introduction/why-rtk-is-redux-today

  Unfortunately, many tutorials are still showing legacy "hand-written" Redux patterns, which result in a much worse experience for users. New learners going through a bootcamp or an outdated Udemy course just follow the examples they're being shown, don't know that RTK is the better and recommended approach, and don't even think to look at our docs.

  Given that, the goal is to provide them with a visual indicator in their editor, like createStore . When users hover over the createStore import or function call, the doc tooltip recommends using configureStore from RTK instead, and points them to that docs page. We hope that new learners will see the strikethrough, read the tooltip, read the docs page, learn about RTK, and begin using it.

  To be extremely clear:

  WE ARE NOT GOING TO ACTUALLY REMOVE THE createStore API, AND ALL YOUR EXISTING CODE WILL STILL CONTINUE TO WORK AS-IS!

  We are just marking createStore as "deprecated":

  "the discouragement of use of some feature or practice, typically because it has been superseded or is no longer considered efficient or safe, without completely removing it or prohibiting its use"

  For additional details, see the extensive discussion in #4325 .

  Rationale

  • RTK provides a vastly improved Redux usage experience, with APIs that simplify standard usage patterns and eliminate common bugs like accidental mutations
  • We've had suggestions to merge all of RTK into the redux core package, or fully deprecate the entire redux package and rename it to @ reduxjs/core. Unfortunately, those bring up too many complexities:
    • We already had a package rename from redux-starter-kit to @ reduxjs/toolkit, and all of our docs and tutorials have pointed to it for the last three years. I don't want to put users through another whiplash package transition for no real benefit
    • Merging or rearranging our packages would effectively require merging all of the Redux repos into a single monorepo. That would require hundreds of hours of effort from us maintainers, including needing to somehow merge all of our docs sites together. We don't have the time to do that.
  • I don't want to add runtime warnings that would be really annoying

  So, this is the minimum possible approach we can take to reach out to users who otherwise would never know that they are following outdated patterns, while avoiding breaking running user code or having to completely rewrite our package and repo structure.

  Results

  When a user imports createStore in their editor, they will see a visual strikethrough. Hovering over it will show a doc tooltip that encourages them to use configureStore from RTK, and points to an explanatory docs page:

  

  Again, no broken code, and no runtime warnings.

  If users do not want to see that strikethrough, they have three options:

  • Follow our suggestion to switch over to Redux Toolkit and configureStore
  • Do nothing. It's just a visual strikethrough, and it doesn't affect how your code behaves. Ignore it.
  • Switch to using the legacy_createStore API that is now exported, which is the exact same function but with no @ deprecation tag. The simplest option is to do an aliased import rename:

  

  What's Changed

  • Mark createStore as deprecated, and add legacy_createStore alias by @ markerikson in #4336

  Full Changelog: v4.1.2...v4.2.0

from redux GitHub release notes

Package name: redux-thunk

• 2.4.2 - 2022-11-04
  

  This release removes an unused TS type that caused errors when users were type-checking libraries in node_modules.

  What's Changed

  • Remove unused type by @ antoniopresto in #328

  Full Changelog: v2.4.1...v2.4.2

• 2.4.1 - 2021-11-26
  

  This release adds an explicit plain action overload to the ThunkDispatch TS type to better handle inference of the return value in some cases.

  What's Changed

  • Improve action return value resolution by @ markerikson in #327

  Full Changelog: v2.4.0...v2.4.1

from redux-thunk GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs