fix(security): bump nodemailer 9.0.0 β 9.0.1#4773
Conversation
There was a problem hiding this comment.
Argus fast-track review β PR #4773 (HIGH security fix, supersedes #4772)
Substance: PASS β Identical nodemailer bump to #4772: ^9.0.0 β ^9.0.1 in package.json + lockfile update. Version numbers correct, integrity hash updated.
Additional change in #4773: Alphabetical reordering of optionalDependencies (ioredis before playwright) β harmless formatting, no functional impact.
CI: ALL GREEN β β 14/14 checks pass, including:
- Trivy SCA (root) β PASS (security gate cleared)
- helm-smoke β PASS (was pending on #4772)
- test (ubuntu-20) β PASS (was pending on #4772)
- test (ubuntu-22) β PASS (was pending on #4772)
- All other checks: PASS
Gate status:
- Gate 1 (review): β This review
- Gate 2 (no conflicts): β mergeable=True
- Gate 3 (CI green): β ALL 14 checks PASS
- Gate 4 (no regressions): β No code changes, dependency bump only
- Gate 5 (unit tests): N/A β no code changes
- Gate 6 (E2E/UAT): N/A β no functional changes
- Gate 7 (documented): β PR body explains security context
- Gate 8 (security clean): β Trivy green, no secrets
- Gate 9 (targets develop): β base=develop
All 9 gates PASS.
App-authored PR note: Opened by aegis-gh-agent[bot]. Per established workflow, requires human approval before merge.
Action: Supersedes #4772 (same change, #4773 has all CI green + minor formatting fix). Closing #4772 as duplicate.
Request: @OneStepAt4time (Boss) β please approve for immediate merge. This is a HIGH security fix that resolves the nodemailer vuln and unblocks develop CI.
OneStepAt4time
left a comment
There was a problem hiding this comment.
Security fix, all gates green. Approved for merge.
Closes: #4765 (wrong-base dependabot PR, closed as
not_planned)What: Bumps nodemailer from 9.0.0 to 9.0.1 to address HIGH vulnerability.
Scope: Single dependency bump. 2 files changed, 7 insertions(+), 7 deletions(-).
Fast-track: HIGH severity security fix. Minimal change, no review delay needed.
Helm-smoke note: If helm-smoke fails, check if it's the pre-existing k3d issue (#4558, fixed by #4560) or a new failure mode.