Bump email-validator from 1.1.3 to 2.2.0

[dependabot[bot]]

Bumps email-validator from 1.1.3 to 2.2.0.

Release notes

Sourced from email-validator's releases.

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.

v2.1.1 (February 26, 2024)

• Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.
• When DNS-based deliverability checks fail, in some cases exceptions are now thrown with raise ... from for better nested exception tracking.
• Fixed tests to work when no local resolver can be configured.
• This project is now licensed under the Unlicense (instead of CC0).
• Minor improvements to tests.
• Minor improvements to code style.

v2.1.0

2.1.0 (October 22, 2023)

• Python 3.8+ is now required (support for Python 3.7 was dropped).
• The old email field on the returned ValidatedEmail object, which in the previous version was superseded by normalized, will now raise a deprecation warning if used. See https://stackoverflow.com/q/879173 for strategies to suppress the DeprecationWarning.
• A __version__ module attribute is added.
• The email address argument to validate_email is now marked as positional-only to better reflect the documented usage using the new Python 3.8 feature.

v2.0.0

No release notes provided.

v1.3.1

Version 1.3.1 (January 21, 2023)

• The new SPF 'v=spf1 -all' (reject-all) deliverability check is removed in most cases. It now is performed only for domains that do not have MX records but do have an A/AAAA fallback record.

v1.3.0

Version 1.3.0 (September 18, 2022)

• Deliverability checks now check for 'v=spf1 -all' SPF records as a way to reject more bad domains.
• Special use domain names now raise EmailSyntaxError instead of EmailUndeliverableError since they are performed even if check_deliverability is off.
• New module-level attributes are added to override the default values of the keyword arguments and the special-use domains list.

... (truncated)

Changelog

Sourced from email-validator's changelog.

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.

2.1.1 (February 26, 2024)

• Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.
• When DNS-based deliverability checks fail, in some cases exceptions are now thrown with raise ... from for better nested exception tracking.
• Fixed tests to work when no local resolver can be configured.
• This project is now licensed under the Unlicense (instead of CC0).
• Minor improvements to tests.
• Minor improvements to code style.

2.1.0 (October 22, 2023)

• Python 3.8+ is now required (support for Python 3.7 was dropped).
• The old email field on the returned ValidatedEmail object, which in the previous version was superseded by normalized, will now raise a deprecation warning if used. See https://stackoverflow.com/q/879173 for strategies to suppress the DeprecationWarning.
• A __version__ module attribute is added.
• The email address argument to validate_email is now marked as positional-only to better reflect the documented usage using the new Python 3.8 feature.

2.0.0 (April 15, 2023)

This is a major update to the library, but since email address specs haven't changed there should be no significant changes to which email addresses are considered valid or invalid with default options. There are new options for accepting unusual email addresses that were previously always rejected, some changes to how DNS errors are handled, many changes in error message text, and major internal improvements including the addition of type annotations. Python 3.7+ is now required. Details follow:

• Python 2.x and 3.x versions through 3.6, and dnspython 1.x, are no longer supported. Python 3.7+ with dnspython 2.x are now required.
• The dnspython package is no longer required if DNS checks are not used, although it will install automatically.
• NoNameservers and NXDOMAIN DNS errors are now handled differently: NoNameservers no longer fails validation, and NXDOMAIN now skips checking for an A/AAAA fallback and goes straight to failing validation.
• Some syntax error messages have changed because they are now checked explicitly rather than as a part of other checks.
• The quoted-string local part syntax (e.g. multiple @-signs, spaces, etc. if surrounded by quotes) and domain-literal addresses (e.g. @[192.XXX...] or @[IPv6:...]) are now parsed but not considered valid by default. Better error messages are now given for these addresses since it can be confusing for a technically valid address to be rejected, and new allow_quoted_local and allow_domain_literal options are added to allow these addresses if you really need them.
• Some other error messages have changed to not repeat the email address in the error message.
• The email field on the returned ValidatedEmail object has been renamed to normalized to be clearer about its importance, but access via .email is also still supported.
• Some mailbox names like postmaster are now normalized to lowercase per RFC 2142.
• The library has been reorganized internally into smaller modules.

... (truncated)

Commits

• 6589b1e Version 2.2.0
• 8051347 Improve the error message for invalid characters in domain names after Unicod...
• 7f1f281 Check domain syntax after normalization to internationalized characters as a ...
• c23c0d6 Improve the error message for IDNA domains being too long by handling the len...
• 452e0ca Add tests for domain label length
• f8709e8 Check that email address length is valid on the original email address string...
• 9ef1f82 Check that the local part is valid after Unicode NFC normalization to prevent...
• 1fb55d4 Add a test that shows that the local part is returned with Unicode NFC normal...
• 3426885 Several fixes for parsing display names
• 0b22c13 Merge point release branch for version 2.1.2
• 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show 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)