Skip to content

fix(deps): update dependency @hookform/resolvers to v5#103

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/hookform-resolvers-5.x
Open

fix(deps): update dependency @hookform/resolvers to v5#103
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/hookform-resolvers-5.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 10, 2025

This PR contains the following updates:

Package Change Age Confidence
@hookform/resolvers (source) ^2.9.11^5.0.0 age confidence

Release Notes

react-hook-form/resolvers (@​hookform/resolvers)

v5.2.2

Compare Source

Bug Fixes

v5.2.1

Compare Source

Bug Fixes

v5.2.0

Compare Source

Features

v5.1.1

Compare Source

Bug Fixes

v5.1.0

Compare Source

Features
  • support Zod 4, Zod v4 mini, and retains compatibility with Zod v3. (#​777) (8d083bd)

v5.0.1

Compare Source

Bug Fixes
  • relax version constraint for react-hook-form 7.55.0 → ^7.55.0 (#​758) (6e88393)

v5.0.0

Compare Source

Features
BREAKING CHANGES
  • Requires react-hook-form@​7.55.0 or higher

Before
Prior to V5, some projects used manual types like

useForm<FormValues>();

After
With V5, the correct approach is:

useForm<Input, Context, Output>();
useForm<FormInputValues, Context, FormOutputValues>();

This update enables distinct outputs when utilizing features like transform from validation libraries.

ℹ️ The best approach is to let the types be inferred from your schema, rather than manually defining them.

v4.1.3

Compare Source

Bug Fixes
  • escape square brackets in field name regex pattern (#​752) (50dd4ad)

v4.1.2

Compare Source

Bug Fixes

v4.1.1

Compare Source

Bug Fixes
  • standard-schema: Propertly handle object path segments (#​746) (8ffada0)

v4.1.0

Compare Source

Features

v4.0.0

Compare Source

Bug Fixes
  • add support for names option (#​713) (985c48d)
  • arktypeResolver: resolve type error when schema is defined from an ArkType scope (#​732) (3233667)
  • handle raw: true option to pass form submission values correctly (#​733) (7807f95)
  • validateFieldsNatively: handle undefined object when reading 'refs' (#​734) (3da2054)
Features
  • ajv: Keep original validation type while using errorMessage (#​728) (5030a59)
  • effectResolver: returns either all errors or only the first one based on criteriaMode (#​737) (12d7d8e)
  • standard-schema: add standard-schema resolver (#​738) (b75a95a)
BREAKING CHANGES
  • ajv: The AJV Resolver now unwraps the errorMessage object to return the original error types. This update may introduce breaking changes to your projects.

v3.10.0

Compare Source

Features

v3.9.1

Compare Source

Bug Fixes

v3.9.0

Compare Source

Features
  • fluentvalidation-ts: add fluentvalidation-ts resolver (#​702) (5fc1e63)
import { useForm } from 'react-hook-form';
import { fluentValidationResolver } from '@&#8203;hookform/resolvers/fluentvalidation-ts';
import { Validator } from 'fluentvalidation-ts';

class FormDataValidator extends Validator<FormData> {
  constructor() {
    super();

    this.ruleFor('username')
      .notEmpty()
      .withMessage('username is a required field');
    this.ruleFor('password')
      .notEmpty()
      .withMessage('password is a required field');
  }
}

const App = () => {
  const { register, handleSubmit } = useForm({
    resolver: fluentValidationResolver(new FormDataValidator()),
  });

  return (
    <form onSubmit={handleSubmit((d) => console.log(d))}>
      <input {...register('username')} />
      {errors.username && <span role="alert">{errors.username.message}</span>}
      <input {...register('password')} />
      {errors.password && <span role="alert">{errors.password.message}</span>}
      <button type="submit">submit</button>
    </form>
  );
};

v3.8.0

Compare Source

Features

v3.7.0

Compare Source

Bug Fixes
  • zodResolver: cannot read properties of undefined (reading 'length') (a3e50c6)
  • chore: update valibot dependency to version >=0.33.0 (#​695)
Features
import { useForm } from 'react-hook-form';
import { vineResolver } from '@&#8203;hookform/resolvers/vine';
import vine from '@&#8203;vinejs/vine';

const schema = vine.compile(
  vine.object({
    username: vine.string().minLength(1),
    password: vine.string().minLength(1),
  }),
);

const App = () => {
  const { register, handleSubmit } = useForm({
    resolver: vineResolver(schema),
  });

  return (
    <form onSubmit={handleSubmit((d) => console.log(d))}>
      <input {...register('username')} />
      {errors.username && <span role="alert">{errors.username.message}</span>}
      <input {...register('password')} />
      {errors.password && <span role="alert">{errors.password.message}</span>}
      <button type="submit">submit</button>
    </form>
  );
};

v3.6.0

Compare Source

Features

v3.5.0

Compare Source

Features

v3.4.2

Compare Source

Bug Fixes

v3.4.1

Compare Source

Bug Fixes

v3.4.0

Compare Source

Features

v3.3.4

Compare Source

Bug Fixes
  • error handling for array errors with root error (1bfc6ab)

v3.3.3

Compare Source

Bug Fixes

v3.3.2

Compare Source

Bug Fixes

v3.3.1

Compare Source

Bug Fixes

v3.3.0

Compare Source

Bug Fixes
Features
  • add support for root errors for field array (#​621) (5f1a622)
  • pass field names and a context as arguments to a Vest suite (#​584) (3519701)
  • valibot: add more tests, support of criteriaMode and reduce size (#​620) (a9d319d)

v3.2.0

Compare Source

Features

v3.1.1

Compare Source

BREAKING CHANGES

Bug Fixes

You don't need to explicitly provide the type when using the useForm function because it automatically infers the types from the Yup schema.

Before

const schema = Yup.shape({ name: string });

const { register } = useForm<{name: string}>({ resolver: yupResolver(schema) });

After

const schema = Yup.shape({ name: string });

const { register } = useForm({ resolver: yupResolver(schema) });

v3.1.0

Compare Source

Features

v3.0.1

Compare Source

Bug Fixes

v3.0.0

Compare Source

BREAKING CHANGES
  • Yup resolver require Yup v1
  • rename rawValues option to raw
  • classValidationResolver: schema options now includes validator and transformer options
  • Please note that ajv and ajv-errors need to be installed separately, as they are not bundled with resolvers

Before:

schemaOptions?: ValidatorOptions,

After:

schemaOptions?: {
    validator?: ValidatorOptions;
    transformer?: ClassTransformOptions;
  }
Bug Fixes
Features
import { useForm } from 'react-hook-form';
import { typeboxResolver } from '@&#8203;hookform/resolvers/typebox';
import { Type } from '@&#8203;sinclair/typebox';

const schema = Type.Object({
  username: Type.String({ minLength: 1 }),
  password: Type.String({ minLength: 1 }),
});

const App = () => {
  const { register, handleSubmit } = useForm({
    resolver: typeboxResolver(schema),
  });

  return (
    <form onSubmit={handleSubmit((d) => console.log(d))}>
      <input {...register('username')} />
      <input type="password" {...register('password')} />
      <input type="submit" />
    </form>
  );
};
Performance Improvements

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 renovate bot force-pushed the renovate/hookform-resolvers-5.x branch 2 times, most recently from eea388c to 4198b3b Compare August 19, 2025 13:44
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from 4198b3b to 3466493 Compare August 31, 2025 13:43
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from 3466493 to 8ed4759 Compare September 14, 2025 09:50
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from 8ed4759 to df90226 Compare September 25, 2025 20:53
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch 2 times, most recently from dbb2248 to 52fa248 Compare October 22, 2025 20:22
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from 52fa248 to c80dfb7 Compare November 10, 2025 21:37
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from c80dfb7 to 93db762 Compare November 18, 2025 12:12
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from 93db762 to 4dcd7f3 Compare December 3, 2025 18:39
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from 4dcd7f3 to a69371e Compare December 31, 2025 17:09
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from a69371e to c88d59f Compare January 8, 2026 18:23
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch 2 times, most recently from 3db8e3f to e358b08 Compare January 23, 2026 20:11
@renovate renovate bot changed the title Update dependency @hookform/resolvers to v5 fix(deps): update dependency @hookform/resolvers to v5 Jan 27, 2026
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from e358b08 to cb4e5a8 Compare February 2, 2026 17:55
@renovate renovate bot force-pushed the renovate/hookform-resolvers-5.x branch from cb4e5a8 to 34760d5 Compare February 12, 2026 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants