chore(deps): bump email-validator from 2.1.1 to 2.3.0

[dependabot]

Bumps email-validator from 2.1.1 to 2.3.0.

Release notes

Sourced from email-validator's releases.

v2.3.0

• The package name is changed from using an underscore (email_validator) to a dash (email-validator) to match PyPi's normalized package name.
• The library no longer checks that the local part is at most 64 characters because a more careful reading of RFC 5321 indicates the limit is optional and such email addresses have been found in the wild. However the check can be restored using a new strict=True parameter, and the overall 254 character email address length limit is still in place.
• New EmailSyntaxError messages are used for some exiting syntax errors related to @-sign homoglyphs and invalid characters in internationalized domains.
• When using allow_display_name=True, display names are now returned with Unicode NFC normalization.
• TypeError is now raised if something other than str (or bytes) is passed as the email address.

2.2.0 (June 20, 2024)

• Email addresses with internationalized local parts could, with rare Unicode characters, be returned as valid but actually be invalid in their normalized form (returned in the normalized field). Local parts now re-validated after Unicode NFC normalization to ensure that invalid characters cannot be injected into the normalized address and that characters with length-increasing NFC normalizations cannot cause a local part to exceed the maximum length after normalization.
• The length check for email addresses with internationalized local parts is now also applied to the original address string prior to Unicode NFC normalization, which may be longer and could exceed the maximum email address length, to protect callers who do not use the returned normalized address.
• Improved error message for IDNA domains that are too long or have invalid characters after Unicode normalization.
• A new option to parse My Name <address@domain> strings, i.e. a display name plus an email address in angle brackets, is now available. It is off by default.
• Improvements to Python typing.
• Some additional tests added.

v2.1.2

2.1.2 (June 16, 2024)

• The domain name length limit is corrected from 255 to 253 IDNA ASCII characters. I misread the RFCs.
• When a domain name has no MX record but does have an A or AAAA record, if none of the IP addresses in the response are globally reachable (i.e. not Private-Use, Loopback, etc.), the response is treated as if there was no A/AAAA response and the email address will fail the deliverability check.
• When a domain name has no MX record but does have an A or AAAA record, the mx field in the object returned by validate_email incorrectly held the IP addresses rather than the domain itself.
• Fixes in tests.

Changelog

Sourced from email-validator's changelog.

2.3.0 (August 26, 2025)

• The package name is changed from using an underscore (email_validator) to a dash (email-validator) to match PyPi's normalized package name.
• The library no longer checks that the local part is at most 64 characters because a more careful reading of RFC 5321 indicates the limit is optional and such email addresses have been found in the wild. However the check can be restored using a new strict=True parameter, and the overall 254 character email address length limit is still in place.
• New EmailSyntaxError messages are used for some exiting syntax errors related to @-sign homoglyphs and invalid characters in internationalized domains.
• When using allow_display_name=True, display names are now returned with Unicode NFC normalization.
• TypeError is now raised if something other than str (or bytes) is passed as the email address.

2.2.0 (June 20, 2024)

• Email addresses with internationalized local parts could, with rare Unicode characters, be returned as valid but actually be invalid in their normalized form (returned in the normalized field). In particular, it is possible to get a normalized address with a ";" character, which is not valid and could change the interpretation of the address. Local parts now re-validated after Unicode NFC normalization to ensure that invalid characters cannot be injected into the normalized address and that characters with length-increasing NFC normalizations cannot cause a local part to exceed the maximum length after normalization. Thanks to khanh@calif.io from https://calif.io for reporting the issue.
• The length check for email addresses with internationalized local parts is now also applied to the original address string prior to Unicode NFC normalization, which may be longer and could exceed the maximum email address length, to protect callers who do not use the returned normalized address.
• Improved error message for IDNA domains that are too long or have invalid characters after Unicode normalization.
• A new option to parse My Name <address@domain> strings, i.e. a display name plus an email address in angle brackets, is now available. It is off by default.
• Improvements to Python typing.
• Some additional tests added.

2.1.2 (June 16, 2024)

• The domain name length limit is corrected from 255 to 253 IDNA ASCII characters. I misread the RFCs.
• When a domain name has no MX record but does have an A or AAAA record, if none of the IP addresses in the response are globally reachable (i.e. not Private-Use, Loopback, etc.), the response is treated as if there was no A/AAAA response and the email address will fail the deliverability check.
• When a domain name has no MX record but does have an A or AAAA record, the mx field in the object returned by validate_email incorrectly held the IP addresses rather than the domain itself.
• Fixes in tests.

Commits

• 030a63a Version 2.3.0
• e943a0f Raise TypeError when an invalid argument is passed for email, closes #155
• f90d256 Remove local part length check unless new strict flag is given, fixes #158
• 98800ba Add explicit checks for internationalized domain name characters invalid unde...
• 936aead Fix final syntax checks on normalized internationalized domains checking the ...
• 8043de4 NFC-normalize display names per UTS #39
• bc08faa Add one-off error messages for full-width-at and small-commercial-at which ar...
• a1c90ab Split exceptions_types.py into exceptions.py and types.py
• dbcf07c Change package name from using underscore to dash to match PyPi normalized pa...
• 7c22208 Support ALLOW_DISPLAY_NAME and ALLOW_EMPTY_LOCAL in the CLI (#145)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)