Skip to content

Change year from 2025 to 2026 in README#3400

Open
CH-USAMA wants to merge 1 commit intoresend:canaryfrom
CH-USAMA:patch-1
Open

Change year from 2025 to 2026 in README#3400
CH-USAMA wants to merge 1 commit intoresend:canaryfrom
CH-USAMA:patch-1

Conversation

@CH-USAMA
Copy link
Copy Markdown

@CH-USAMA CH-USAMA commented Apr 19, 2026

Updated the year in the rationale for modern email development.


Summary by cubic

Update the README “Why” section to reference 2026 instead of 2025, keeping the rationale current.

Written for commit 45ea8b7. Summary will update on new commits.

Updated the year in the rationale for modern email development.
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 19, 2026

@CH-USAMA is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 19, 2026

⚠️ No Changeset found

Latest commit: 45ea8b7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

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.

1 participant