Bump email-validator from 2.1.0.post1 to 2.1.1 #7269
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [email-validator](https://github.com/JoshData/python-email-validator) from 2.1.0.post1 to 2.1.1. - [Release notes](https://github.com/JoshData/python-email-validator/releases) - [Changelog](https://github.com/JoshData/python-email-validator/blob/main/CHANGELOG.md) - [Commits](https://github.com/JoshData/python-email-validator/commits/v2.1.1) --- updated-dependencies: - dependency-name: email-validator dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
inmantaci
approved these changes
Feb 27, 2024
|
Processing this pull request |
|
Merged into branches iso7 in 65798bc |
inmantaci
pushed a commit
that referenced
this pull request
Feb 27, 2024
Bumps [email-validator](https://github.com/JoshData/python-email-validator) from 2.1.0.post1 to 2.1.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/JoshData/python-email-validator/releases">email-validator's releases</a>.</em></p> <blockquote> <h2>v2.1.1 (February 26, 2024)</h2> <ul> <li>Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.</li> <li>When DNS-based deliverability checks fail, in some cases exceptions are now thrown with <code>raise ... from</code> for better nested exception tracking.</li> <li>Fixed tests to work when no local resolver can be configured.</li> <li>This project is now licensed under the Unlicense (instead of CC0).</li> <li>Minor improvements to tests.</li> <li>Minor improvements to code style.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/JoshData/python-email-validator/blob/main/CHANGELOG.md">email-validator's changelog</a>.</em></p> <blockquote> <h2>2.1.1 (February 26, 2024)</h2> <ul> <li>Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.</li> <li>When DNS-based deliverability checks fail, in some cases exceptions are now thrown with <code>raise ... from</code> for better nested exception tracking.</li> <li>Fixed tests to work when no local resolver can be configured.</li> <li>This project is now licensed under the Unlicense (instead of CC0).</li> <li>Minor improvements to tests.</li> <li>Minor improvements to code style.</li> </ul> <h2>2.1.0 (October 22, 2023)</h2> <ul> <li>Python 3.8+ is now required (support for Python 3.7 was dropped).</li> <li>The old <code>email</code> field on the returned <code>ValidatedEmail</code> object, which in the previous version was superseded by <code>normalized</code>, will now raise a deprecation warning if used. See <a href="https://stackoverflow.com/q/879173">https://stackoverflow.com/q/879173</a> for strategies to suppress the DeprecationWarning.</li> <li>A <code>__version__</code> module attribute is added.</li> <li>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.</li> </ul> <h2>2.0.0 (April 15, 2023)</h2> <p>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:</p> <ul> <li>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.</li> <li>The dnspython package is no longer required if DNS checks are not used, although it will install automatically.</li> <li>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.</li> <li>Some syntax error messages have changed because they are now checked explicitly rather than as a part of other checks.</li> <li>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.</li> <li>Some other error messages have changed to not repeat the email address in the error message.</li> <li>The <code>email</code> field on the returned <code>ValidatedEmail</code> object has been renamed to <code>normalized</code> to be clearer about its importance, but access via <code>.email</code> is also still supported.</li> <li>Some mailbox names like <code>postmaster</code> are now normalized to lowercase per RFC 2142.</li> <li>The library has been reorganized internally into smaller modules.</li> <li>The tests have been reorganized and expanded. Deliverability tests now mostly use captured DNS responses so they can be run off-line.</li> <li>The <strong>main</strong> tool now reads options to validate_email from environment variables.</li> <li>Type annotations have been added to the exported methods and the ValidatedEmail class and some internal methods.</li> <li>The old dict-like pattern for the return value of validate_email is deprecated.</li> </ul> <p>Versions 2.0.0.post1 and 2.0.0.post2 corrected some packaging issues. 2.0.0.post2 also added a check for an invalid combination of arguments.</p> <h2>Version 1.3.1 (January 21, 2023)</h2> <ul> <li>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.</li> </ul> <h2>Version 1.3.0 (September 18, 2022)</h2> <ul> <li>Deliverability checks now check for 'v=spf1 -all' SPF records as a way to reject more bad domains.</li> <li>Special use domain names now raise EmailSyntaxError instead of EmailUndeliverableError since they are performed even if check_deliverability is off.</li> <li>New module-level attributes are added to override the default values of the keyword arguments and the special-use domains list.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/JoshData/python-email-validator/commits/v2.1.1">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 <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) </details>
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps email-validator from 2.1.0.post1 to 2.1.1.
Release notes
Sourced from email-validator's releases.
Changelog
Sourced from email-validator's changelog.
... (truncated)
Commits
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)