Bump resend from 0.27.0 to 1.0.0

[dependabot]

Bumps resend from 0.27.0 to 1.0.0.

Release notes

Sourced from resend's releases.

v1.0.0

What's Changed

• chore: Update broadcasts example to include new attrs by @​drish in resend/resend-ruby#133
• chore(deps): update dependency rspec to v3.13.2 by @​renovate[bot] in resend/resend-ruby#137
• feat: Impl Topics API by @​drish in resend/resend-ruby#136
• feat: Inbound API by @​drish in resend/resend-ruby#134
• feat: Impl templates API by @​drish in resend/resend-ruby#135
• feat: webhooks API support by @​drish in resend/resend-ruby#139
• feat: make new attachments API conform to updated spec by @​lucasfcosta in resend/resend-ruby#140
• feat: contact properties + contact topic update/get by @​drish in resend/resend-ruby#144
• release/v1.0.0 by @​drish in resend/resend-ruby#146

New Contributors

• @​lucasfcosta made their first contribution in resend/resend-ruby#140

Full Changelog: resend/resend-ruby@v0.26.0...v1.0.0

Changelog

Sourced from resend's changelog.

[1.0.0] - 2025-10-31

Overview

This major release introduces breaking changes to the Contacts API and deprecates the Audiences API in favor of Segments. If you only use the SDK for sending emails or the Audiences API, you can upgrade to v1.0.0 without any code changes. The breaking changes are limited to the Contacts API only.

⚠️ BREAKING CHANGES

Contacts API Changes

• ⚠️ Change Contacts.create to accept hash parameter with optional audience_id - Previously required audience_id in params, now it's optional. Supports global contacts.
• ⚠️ Change Contacts.get from get(audience_id, id) to get(params) - Now accepts a hash with optional audience_id and required id or email. Raises ArgumentError: "Missing \id` or `email` field"` when neither is provided.
• ⚠️ Change Contacts.list from list(audience_id, params = {}) to list(params = {}) - Now accepts a hash with optional audience_id and pagination params
• ⚠️ Change Contacts.remove from remove(audience_id, contact_id) to remove(params) - Now accepts a hash with optional audience_id and required id or email. Raises ArgumentError: "Missing \id` or `email` field"` when neither is provided.
• ⚠️ Change Contacts.update error message - Error changed from "id or email is required" to "Missing \id` or `email` field"` to match Node.js SDK format
• ⚠️ Change Contacts.update to accept optional audience_id - Previously required audience_id in params, now it's optional

Before (v0.x):

# Methods used positional arguments and required audience_id
Resend::Contacts.create(audience_id: "aud_123", email: "user@example.com", first_name: "John")
contact = Resend::Contacts.get("aud_123", "contact_123")
contacts = Resend::Contacts.list("aud_123")
contacts = Resend::Contacts.list("aud_123", limit: 10)
Resend::Contacts.update(audience_id: "aud_123", id: "contact_123", first_name: "Jane")
Resend::Contacts.remove("aud_123", "contact_123")

After (v1.0.0):

# Methods use hash parameters and support optional audience_id
# Global contacts (no audience_id)
Resend::Contacts.create(email: "user@example.com", first_name: "John")
contact = Resend::Contacts.get(id: "contact_123")
contact = Resend::Contacts.get(email: "user@example.com")
contacts = Resend::Contacts.list
contacts = Resend::Contacts.list(limit: 10)
Resend::Contacts.update(id: "contact_123", first_name: "Jane")
Resend::Contacts.remove(id: "contact_123")
Audience-scoped contacts (with audience_id)
Resend::Contacts.create(audience_id: "aud_123", email: "user@example.com", first_name: "John")
contact = Resend::Contacts.get(audience_id: "aud_123", id: "contact_123")
contacts = Resend::Contacts.list(audience_id: "aud_123", limit: 10)
Resend::Contacts.update(audience_id: "aud_123", id: "contact_123", first_name: "Jane")
Resend::Contacts.remove(audience_id: "aud_123", id: "contact_123")

... (truncated)

Commits

• 990276a release/v1.0.0 (#146)
• db7a739 feat: contact properties + contact topic update/get (#144)
• 910b5eb chore: Bump to v0.27.0 (#143)
• 303c74e feat: make new attachments API conform to updated spec (#140)
• 259b98e feat: webhooks API support (#139)
• 6fc9529 feat: Impl templates API (#135)
• 3f7027c feat: Inbound API (#134)
• a7dd876 feat: Impl Topics API (#136)
• 2f8068c chore(deps): update dependency rspec to v3.13.2 (#137)
• 4feae1c chore: Update broadcasts example to include new attrs (#133)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[icole]

@dependabot rebase

[icole]

@dependabot rebase

[sentry]

Bug: The major version bump of the resend gem to v1.0.0 may introduce unverified breaking API changes, potentially affecting methods like Resend::Batch.send and causing email delivery to fail.
_{Severity: MEDIUM}

Suggested Fix

Before merging, verify the resend gem v1.0.0 changelog or documentation for any breaking changes to the Resend::Batch.send and Resend::Emails.send methods. Confirm that the parameter names, method signatures, and error classes remain compatible with the existing implementation. Add thorough testing for the email-sending functionality in a staging environment to ensure it operates correctly with the new version.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: Gemfile.lock#L654

Potential issue: The update of the `resend` gem from version 0.27.0 to 1.0.0 is a major
version change, which often indicates breaking API modifications. While specific
breaking changes affecting the application's usage of `Resend::Batch.send` and
`Resend::Emails.send` could not be confirmed due to a lack of accessible documentation,
the risk of such changes exists. A failure in these methods would prevent the
application from sending emails, such as meal and RSVP reminders. The analysis could not
verify the exact API contract for v1.0.0, making the likelihood of this issue uncertain.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[dependabot]

Superseded by #118.