chore(deps): bump nodemailer from 8.0.4 to 8.0.5 in /packages/email#5815
chore(deps): bump nodemailer from 8.0.4 to 8.0.5 in /packages/email#5815dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [nodemailer](https://github.com/nodemailer/nodemailer) from 8.0.4 to 8.0.5. - [Release notes](https://github.com/nodemailer/nodemailer/releases) - [Changelog](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md) - [Commits](nodemailer/nodemailer@v8.0.4...v8.0.5) --- updated-dependencies: - dependency-name: nodemailer dependency-version: 8.0.5 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Dependency bump from nodemailer 8.0.4 to 8.0.5 was reviewed with no issues found and appears safe to merge.
Status: No Issues Found | Risk: Low
Review Details
📁 1 files reviewed | 💬 0 comments
Instruction Files
└── .claude/
├── agents/
│ └── nango-docs-migrator.md
└── skills
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0224f406d7
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "form-data": "4.0.4", | ||
| "mailgun.js": "12.0.1", | ||
| "nodemailer": "8.0.4", | ||
| "nodemailer": "8.0.5", |
There was a problem hiding this comment.
Regenerate lockfile after bumping nodemailer
This version bump only updates packages/email/package.json, but package-lock.json still pins packages/email and node_modules/nodemailer to 8.0.4 (e.g., around line 33825), so the repository’s locked install state does not match the declared dependency. I checked the CI workflows and they run npm ci (for example, .github/workflows/tests.yaml and .github/workflows/deploy.yaml), so this change can leave CI and production installs on the old package or fail on lock/manifest drift instead of actually applying the 8.0.5 security fix.
Useful? React with 👍 / 👎.
|
Looks like nodemailer is up-to-date now, so this is no longer needed. |
Bumps nodemailer from 8.0.4 to 8.0.5.
Release notes
Sourced from nodemailer's releases.
Changelog
Sourced from nodemailer's changelog.
Commits
202cfb3chore(master): release 8.0.5 (#1809)b634abfdocs: add CLAUDE.md with project conventions and release process95876b1fix: decode SMTP server responses as UTF-8 at line boundary0a43876fix: sanitize CRLF in transport name option to prevent SMTP command injection...08e59e6chore: update dev dependenciesDependabot 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.
This is a narrowly scoped maintenance update in the
@nangohq/emailpackage that only bumpsnodemailerfrom8.0.4to8.0.5inpackages/email/package.json, with no direct changes to local application logic, configuration behavior, or tests. Overall risk is low while still providing security hardening benefits from the upstream patch.This summary was automatically generated by @propel-code-bot