v3.0.0

Major Changes

• Migrate to better-auth v1.5.0 (thanks @samerkh)

v.2.3.1

2.3.1

Patch Changes

• Added missing permissions in release GH action

2.3.0

Minor Changes

• Added support for Czech (cs-CZ) (thanks @michaeldoubek)
• Added support for Captcha plugin

v2.2.2

Patch Changes

• • Added support for az-AZ (Azerbaijani) (thanks @mehdiasadli)
  • Added support for bn-BD (Bengali) (thanks @ktisakib)

v2.2.1

Patch Changes

• Changes on DOC

v2.2.0

Minor Changes

• • Added support for translations in plugins (thanks @ylyra)
  • To contribute a new language, just run pnpm generate:locale and enter the language code, it will generate the new language files for you to edit and add translations (@ylyra is the best)
  • Added support for ckb-IQ (Kurdish Sorani) (thanks @didar-dev)

v2.1.10

Patch Changes

• Added support for ro-RO (Romanian) (thanks @danielavornic)

v2.1.9

Patch Changes

• Fix: Missing error USER_ALREADY_EXISTS_USE_ANOTHER_EMAIL

v2.1.8

Patch Changes

• fix: preserve original error codes in translations (thanks @tockawaffle)

v2.1.7

Patch Changes

• Fixed issue where translations were not applied on server side requests
• Added support for Danish (Thanks @BjornFrancke)

v2.1.6

Patch Changes

• Providing custom translations no longer override the whole translation for used language
  Before when providing a custom translation for a specific error code, the whole translation for the language was overridden.

  localization({
    defaultLocale: "pt-BR",
    translations: {
      "pt-BR": {
        USER_NOT_FOUND: "Usuário não encontrado",
      },
    },
  });

  If any other error code happened, it would fallback to the default translation due to the code missing from the custom translation. Now it will just use the default translation.