Skip to content

Conversation

@snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade nodemailer from 6.4.11 to 6.4.12.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2020-09-30.
Release notes
Package name: nodemailer from nodemailer GitHub release notes
Commit messages
Package name: nodemailer
  • 455cfbe v6.4.12
  • 1787f22 Includes all information from the oath2 error response in the error message (#1191)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@codecov
Copy link

codecov bot commented Oct 21, 2020

Codecov Report

Merging #301 (2787d1f) into master (d081932) will decrease coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #301      +/-   ##
==========================================
- Coverage   87.08%   87.06%   -0.03%     
==========================================
  Files          17       17              
  Lines         635      634       -1     
==========================================
- Hits          553      552       -1     
  Misses         82       82              
Impacted Files Coverage Δ
src/email/index.js 78.57% <0.00%> (-1.43%) ⬇️
src/routes/contact.js 86.33% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update abcabee...4bbe8cb. Read the comment docs.

@blakenan-bellese
Copy link
Contributor

superseded by PR #304

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants