fix(deps): update dependency formik to v2.4.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
formik (source)	2.2.9 -> 2.4.6

---

Release Notes

jaredpalmer/formik (formik)

v2.4.6

Compare Source

Patch Changes

• f57ca9b #​3949 Thanks @​DeveloperRaj! - Changing the state inside formik was changing reference of initialValues provided via props, deep cloning the initialvalues will fix it.

v2.4.5

Compare Source

Patch Changes

• d7db9cd #​3860 Thanks @​patik! - Add missing dependency @types/hoist-non-react-statics, closes #​3837

• fe4ed7e #​3501 Thanks @​markspolakovs! - Mark formik as side-effect free in package.json

v2.4.4

Compare Source

Patch Changes

• 41720c2 #​3862 Thanks @​yazaldefilimonepinto! - Forward className for custom components used with Field

• da58b29 #​3858 Thanks @​alaanescobedo! - Remove use of deprecated StatelessComponent type in favor of FunctionComponent

• 5c01ee7 #​3872 Thanks @​rajpatelbot! - FIX: Fixed resetForm function dependency issue

v2.4.3

Compare Source

Patch Changes

• 9e0a661 #​3843 Thanks @​bonimba! - Fix FormikHelper and FieldHelperProps types

v2.4.2

Compare Source

Patch Changes

• 96280d3 #​3817 Thanks @​probablyup! - Updated internal types to support React 18.

v2.4.1

Compare Source

Patch Changes

• 2b194c2 #​3808 Thanks @​NagaiKoki! - fix type of setFieldValue function

• 708bcb2 #​3813 Thanks @​probablyup! - Revert FieldArray "shouldComponentUpdate" performance optimization. As it turns out, it's a common use case to have JSX controlled via non-Formik state/props inside of FieldArray, so it's not safe to cancel re-renders here.

• 187e47d #​3815 Thanks @​probablyup! - Revert Yup transform support for the time being, this may be re-introduced in a future release under an opt-in prop.

v2.4.0

Compare Source

Minor Changes

• 2f53b70 #​3796 Thanks @​probablyup! - Add support for Yup "transforms".

v2.3.3

Compare Source

Patch Changes

• f075a0c #​3798 Thanks @​probablyup! - Fixed the use of generics for the ArrayHelpers type such that any[] is the default array type and for each individual method the array item type can be overridden if necessary.

v2.3.2

Compare Source

Patch Changes

• f086b5a #​3237 Thanks @​pieplu! - Changed getIn to return undefined when it can't find a value AND a parent of that value is "falsy" ( "" / 0 / null / false )

• 6d8f018 #​3792 Thanks @​probablyup! - Update the type for setFieldValue to reflect the returned Promise and potential returned error(s).

v2.3.0

Compare Source

Minor Changes

• 73de78d #​3788 Thanks @​probablyup! - Added typescript generics to ArrayHelpers interface and its methods so that users who use TypeScript can set the type for their arrays and have type safety on array utils. I have also gone ahead and made supplying a type for the generic optional for the sake of backwards compatibility so any existing TS code that does not give a type for the FieldArray will continue to work as they always have.

• 39a7bf7 #​3786 Thanks @​probablyup! - Yup by default only allows for cross-field validation within the
  same field object. This is not that useful in most scenarios because
  a sufficiently-complex form will have several yup.object() in the
  schema.

  const deepNestedSchema = Yup.object({
    object: Yup.object({
      nestedField: Yup.number().required(),
    }),
    object2: Yup.object({
      // this doesn't work because `object.nestedField` is outside of `object2`
      nestedFieldWithRef: Yup.number()
        .min(0)
        .max(Yup.ref('object.nestedField')),
    }),
  });

  However, Yup offers something called context which can operate across
  the entire schema when using a \$ prefix:

  const deepNestedSchema = Yup.object({
    object: Yup.object({
      nestedField: Yup.number().required(),
    }),
    object2: Yup.object({
      // this works because of the "context" feature, enabled by $ prefix
      nestedFieldWithRef: Yup.number()
        .min(0)
        .max(Yup.ref('$object.nestedField')),
    }),
  });

  With this change, you may now validate against any field in the entire schema,
  regardless of position when using the \$ prefix.

v2.2.10

Compare Source

Patch Changes

• 22e236e #​3784 Thanks @​probablyup! - Improve performance of the FieldArray component by adding a shouldComponentUpdate check; this should help avoid unnecessary re-renders which may affect the performance of a form.

• bc9cb28 #​3785 Thanks @​probablyup! - Fixed field error state for array fields that have an error and become empty through an API like arrayHelpers.remove.

  The prior behavior resolved the field error to [undefined], now it is simply undefined.

• 9cbf150 #​3787 Thanks @​probablyup! - Fix infinite loop issue in Field when field helpers (setTouched, etc) are used as an argument in React.useEffect.

• 9c75a9f #​3780 Thanks @​probablyup! - Fixed an issue with array field errors being incorrectly split into an array of individual characters instead of an array of error strings.

• 35fa4cc #​3783 Thanks @​probablyup! - Fix validation of deep.dot.path field references when using the validateField API.

---

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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ 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: react-scripts@5.0.1
npm ERR! Found: typescript@5.2.2
npm ERR! node_modules/typescript
npm ERR!   typescript@"5.2.2" from the root project
npm ERR!   typescript@"^4.6.4 || ^5.0.0" from @commitlint/load@17.7.2
npm ERR!   node_modules/@commitlint/load
npm ERR!     @commitlint/load@"^17.7.2" from @commitlint/cli@17.7.2
npm ERR!     node_modules/@commitlint/cli
npm ERR!       dev @commitlint/cli@"17.7.2" from the root project
npm ERR!       1 more (commitlint)
npm ERR!   5 more (cosmiconfig, cosmiconfig-typescript-loader, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" 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/2024-04-24T23_12_57_323Z-debug-0.log

[renovate]

⚠️ 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: react-scripts@5.0.1
npm ERR! Found: typescript@5.2.2
npm ERR! node_modules/typescript
npm ERR!   typescript@"5.2.2" from the root project
npm ERR!   typescript@"^4.6.4 || ^5.0.0" from @commitlint/load@17.7.2
npm ERR!   node_modules/@commitlint/load
npm ERR!     @commitlint/load@"^17.7.2" from @commitlint/cli@17.7.2
npm ERR!     node_modules/@commitlint/cli
npm ERR!       dev @commitlint/cli@"17.7.2" from the root project
npm ERR!       1 more (commitlint)
npm ERR!   5 more (cosmiconfig, cosmiconfig-typescript-loader, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" 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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-10-22T00_09_19_672Z-debug-0.log