Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 7, 2025

This PR contains the following updates:

Package Change Age Confidence
resend ^3.2.0 -> ^6.0.0 age confidence

Release Notes

resendlabs/resend-node (resend)

v6.2.2

Compare Source

v6.2.1

Compare Source

v6.2.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v6.1.3...v6.2.0

v6.1.3

Compare Source

What's Changed

Full Changelog: resend/resend-node@v6.1.2...v6.1.3

v6.1.2

Compare Source

What's Changed

Full Changelog: resend/resend-node@v6.1.1...v6.1.2

v6.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: resend/resend-node@v6.1.0...v6.1.1

v6.1.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v6.0.3...v6.1.0

v6.0.3

Compare Source

What's Changed

  • fix: typo in invalid_api_key error name (only a type issue)

Full Changelog: resend/resend-node@v6.0.2...v6.0.3

v6.0.2

Compare Source

v6.0.1

Compare Source

What's Changed

Full Changelog: resend/resend-node@v6.0.0...v6.0.1

v6.0.0

Compare Source

What's Changed

This release updates the contentId parameter on the email attachment schema. While this is a feature still in preview and is yet to be fully released, if you have started to use it already, make sure to update references to inlineContentId in your code to use just contentId instead.

No other breaking changes are introduced. If you were not using the feature mentioned above, no changes are needed.

Full Changelog: resend/resend-node@v5.0.0...v6.0.0

v5.0.0

Compare Source

What's Changed

How to migrate

The breaking change should only affect users that use the react option to send emails, but don't have @react-email/render installed. To properly have it working, you should install it in that case.

[!WARNING]
If you want to upgrade to remove @react-email/render from your project, you should uninstall the SDK npm uninstall resend and install it again npm install resend@latest. This will ensure that @react-email/render doesn't remain in your lockfile in a safe way.

Full Changelog: resend/resend-node@v4.8.0...v5.0.0

v4.8.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v4.7.0...v4.8.0

v4.7.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v4.6.0...v4.7.0

v4.6.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v4.5.2...v4.6.0

v4.5.2

Compare Source

What's Changed

New Contributors

Full Changelog: resend/resend-node@v4.4.1...v4.5.2

v4.5.1

Compare Source

v4.5.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v4.4.1...v4.5.0

v4.4.1

Compare Source

What's Changed

Full Changelog: resend/resend-node@v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

New Contributors

Full Changelog: resend/resend-node@v4.3.0...v4.4.0

v4.3.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v4.2.0...v4.3.0

v4.2.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v4.1.2...v4.2.0

v4.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: resend/resend-node@v4.1.1...v4.1.2

v4.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: resend/resend-node@v4.0.0...v4.1.1

v4.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: resend/resend-node@v4.0.0...v4.0.1

v4.0.0

Compare Source

Major

  • Camel case types resend#418
    • Create email: reply_to -> replyTo
    • Create email: attachments[].content_type -> attachments[].contentType

Minor

Patch

v3.5.0

Compare Source

  • fix: Remove optionality from required types #​401
  • feat: Export all interfaces for Requests and Responses #​396

v3.4.0

Compare Source

Minor

  • Add new content_type property to the Attachment type resend#391
  • Handle network error from fetch so instead of throwing we return the error object resend#389

v3.3.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/resend-6.x branch from 20dea52 to aa7bb01 Compare August 8, 2025 14:34
@renovate renovate bot force-pushed the renovate/resend-6.x branch from aa7bb01 to f82dd7c Compare August 31, 2025 12:00
@renovate renovate bot force-pushed the renovate/resend-6.x branch from f82dd7c to ad2561d Compare September 8, 2025 18:54
@renovate renovate bot force-pushed the renovate/resend-6.x branch from ad2561d to 2a8a294 Compare September 15, 2025 23:50
@renovate renovate bot force-pushed the renovate/resend-6.x branch 2 times, most recently from 14ca7cf to 91aacaa Compare October 1, 2025 22:30
@renovate renovate bot force-pushed the renovate/resend-6.x branch 2 times, most recently from 1a63385 to 52ee4b7 Compare October 18, 2025 02:36
@renovate renovate bot force-pushed the renovate/resend-6.x branch from 52ee4b7 to ecc4f0b Compare October 21, 2025 19:45
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.

0 participants