chore(deps): bump nodemailer from 7.0.11 to 9.0.1#3150
Conversation
Bumps [nodemailer](https://github.com/nodemailer/nodemailer) from 7.0.11 to 9.0.1. - [Release notes](https://github.com/nodemailer/nodemailer/releases) - [Changelog](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md) - [Commits](nodemailer/nodemailer@v7.0.11...v9.0.1) --- updated-dependencies: - dependency-name: nodemailer dependency-version: 9.0.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dosubot
Bot
added
the
size:XS
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM — straightforward dependabot bump; the only nodemailer call-site uses a basic SMTP transport with text/html, which is unaffected by the 9.0 TLS-validation breaking change.
Extended reasoning...
Overview
This is a Dependabot PR bumping nodemailer from 7.0.11 to 9.0.1 (and the corresponding pnpm-lock.yaml churn for transitive AWS SDK / Smithy updates that came along for the ride). Only package.json and pnpm-lock.yaml change.
Security risks
The 9.0.0 release contains an intentional behavioral hardening — TLS certificates are now validated by default when fetching remote content (attachment href/path URLs, OAuth2 token endpoints, HTTP/HTTPS proxy CONNECT). 9.0.1 adds an additional disableFileAccess/disableUrlAccess enforcement for the raw message option. Both are security-positive changes. The breaking change would only impact callers that rely on remote attachments, OAuth2, or proxy CONNECT — none of which are used here.
Level of scrutiny
Low. The only call site is app/api/contact-sales/route.ts, which just creates a transport from SMTP_CONNECTION_URL and calls sendMail with from/to/replyTo/subject/text/html. No attachments, no OAuth2, no proxy — none of the 9.0 breaking-change surface is touched. The @types/nodemailer is still pinned to ^7.0.4, but the API used (createTransport, sendMail) has been stable across major versions, so type drift is unlikely to cause build issues.
Other factors
Vercel preview deploys will catch any unforeseen build/runtime regression before merge. No bugs were flagged by the bug-hunting system, and the change is mechanical.
Bumps nodemailer from 7.0.11 to 9.0.1.
Release notes
Sourced from nodemailer's releases.
... (truncated)
Changelog
Sourced from nodemailer's changelog.
... (truncated)
Commits
69cf625chore(master): release 9.0.1 (#1828)a82e060fix: enforce disableFileAccess/disableUrlAccess for raw message option4e58450chore: update dev dependencies541f5fdchore(master): release 9.0.0 (#1827)0c080fbfix: replace deprecated url.parse with a WHATWG URL wrapper6a947acfix!: validate TLS certificates by default when fetching remote contente3b1bdachore(master): release 8.0.11 (#1826)4358cafrefactor: remove dead checks flagged by Code Quality analysiscf5195cchore: harden workflow token permissions and update GitHub Actions067aebefix: parse Ethereal response props without polynomial regex backtrackingDependabot 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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.