[!WARNING]
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
JoshData/python-email-validator (email-validator)
### [`v2.2.0`](https://redirect.github.com/JoshData/python-email-validator/blob/HEAD/CHANGELOG.md#220-June-20-2024)
[Compare Source](https://redirect.github.com/JoshData/python-email-validator/compare/v2.1.2...v2.2.0)
- 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 ` 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`](https://redirect.github.com/JoshData/python-email-validator/blob/HEAD/CHANGELOG.md#212-June-16-2024)
[Compare Source](https://redirect.github.com/JoshData/python-email-validator/compare/v2.1.1...v2.1.2)
- 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.
Configuration
📅 Schedule: Branch creation - "on saturday" in timezone Asia/Kuala_Lumpur, 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 contains the following updates:
==2.1.1->==2.2.0Release Notes
JoshData/python-email-validator (email-validator)
### [`v2.2.0`](https://redirect.github.com/JoshData/python-email-validator/blob/HEAD/CHANGELOG.md#220-June-20-2024) [Compare Source](https://redirect.github.com/JoshData/python-email-validator/compare/v2.1.2...v2.2.0) - 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 NameConfiguration
📅 Schedule: Branch creation - "on saturday" in timezone Asia/Kuala_Lumpur, 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.
This PR was generated by Mend Renovate. View the repository job log.