chore(deps): update nodemailer, s3 clients#6510
Merged
kschelonka merged 1 commit intomainfrom Feb 25, 2026
Merged
Conversation
codemist
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update some packages that may be causing the 403s in builds on other PRs. I analyzed nodemailer as a dependency in next-auth. The breaking update was a rename of a specific error code from NOAUTH to ENOAUTH. From reading the next-auth source code I don't expect there to be an issue with overriding the dependency to allow v8, but I will test behavior in dev (and we will let bake in stage).
See nextauthjs/next-auth#13180