Skip to content

[Snyk] Security upgrade resend from 3.5.0 to 4.2.0 - #121

Closed
Power-Maverick wants to merge 1 commit into
mainfrom
snyk-fix-ed5d5c8a96ffe1b8913b9b166a0b3615
Closed

Power-Maverick wants to merge 1 commit into
mainfrom
snyk-fix-ed5d5c8a96ffe1b8913b9b166a0b3615

Conversation

@Power-Maverick

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Uncontrolled Recursion
SNYK-JS-BRACEEXPANSION-20244952
  828  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BRACEEXPANSION-20244950
  738  
high severity Uncontrolled Recursion
SNYK-JS-BRACEEXPANSION-20244948
  721  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled Recursion
🦉 Regular Expression Denial of Service (ReDoS)

@Power-Maverick

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This major version upgrade from v3 to v4 introduces breaking changes, most notably in the naming of API parameters.

Key Breaking Change:

  • Parameter Renaming: The reply_to parameter has been renamed to replyTo. Code using the old reply_to parameter will need to be updated to use the new camelCase replyTo parameter to ensure functionality.

This change requires direct code modification to maintain correct behavior. Given the lack of a formal changelog for the v4.0.0 release, there may be other undocumented changes.

Source: GitHub Issue discussing the replyTo change

Recommendation:
Developers should perform a global search for reply_to in their calls to the Resend SDK and replace it with replyTo. Due to the uncertainty around other potential breaking changes, thorough testing of all email-sending functionality is strongly recommended after this upgrade.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@vercel

vercel Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
web Ready Ready Preview Sep 30, 2026 11:27am UTC

This branch was successfully deployed

1 active deployment
Preview — 2f9e5641 Deployed Sep 30, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants