This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of nodemailer.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 48.701% when pulling 61d4d48e3111bfb8bb457bdfef76db1dc1353694 on greenkeeper-nodemailer-3.1.3 into d12cdf22d9bb9e165f7bec3e487c9f5723604e59 on master.
Coverage remained the same at 48.701% when pulling 9446a5c8ce98ac34b48ac865548a37926d5f69ca on greenkeeper-nodemailer-3.1.3 into a60b00529cba3c58e00f562e2a4515297769ca96 on master.
Coverage remained the same at 48.701% when pulling 34bd079fff79fde8774657b0d548c6b4b61a8ae6 on greenkeeper-nodemailer-3.1.3 into ad97438da1a8f39e5180fb70bc367270f6ee5994 on master.
Hello lovely humans,
nodemailer just published its new version 3.1.3.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of nodemailer. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 59 commits .
ef202df
v3.1.3
4397e7f
Added .verify() method for SES. Tries to send mail to invalid address
0097988
v3.1.2
cca3b8c
Add error handling for SES and sendmail tranports for failing messages
315eb22
v3.1.1
aba7bd6
Added missing transport.on('idle') and transport.isIdle() for SES transports
689f834
v3.1.0
3c3d920
Supress Message-ID and Date in DKIM headers when using SES
8819548
updated message-id handling for SES
645dd95
Merge branch 'master' of github.com:nodemailer/nodemailer
5cadb3f
Initial support for SES
1ceab54
Added some missing tests for icalEvent
d78b63b
Added test for json transport
fd7aeff
Merge branch 'master' of github.com:nodemailer/nodemailer
7a6b10b
Updated README
There are 59 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.