chore: bump version to 1.7.0 - #213
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
There was a problem hiding this comment.
No issues found across 10 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.
Auto-approved: This release bundles already-reviewed features into a version bump. The only behavioral change is migrating a single error class, as shown by the diff; no new operational, security, or data-handling decisions are introduced.
Re-trigger cubic
felipefreitag
force-pushed
the
release/v1.7.0
branch
from
July 31, 2026 17:51
f5b7196 to
9264ee5
Compare
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
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.
Stacked on #210. Merge #210 first, then this.
What
Cuts 1.7.0 with the suppressions endpoints (#208) and the 404 error mapping (#210).
Changes
CHANGELOG.md— promote the## [Unreleased]heading from fix(errors): map 404 to NotFoundError instead of InvalidRequestError #210 to## [1.7.0] - 2026-07-31, and add the suppressions entry above the existing### Changedblock. Repoint the 404 link from issue NotFoundError is never raised: ERRORS maps 404 to InvalidRequestError #209 to PR fix(errors): map 404 to NotFoundError instead of InvalidRequestError #210, to match how the 1.6.0 entries link PRs.CHANGELOG.md— add the missing compare-link definitions for[1.7.0]and[1.6.0]. Only[1.0.0]had one, so the 1.6.0 heading has rendered as literal brackets since it was added.lib/resend/version.rb—1.6.0->1.7.0Gemfile.lock—resend (1.6.0)->resend (1.7.0)Version choice
1.7.0, not 2.0.0.
The 404 change is breaking for code that rescues
InvalidRequestErrorspecifically to catch 404s, so strict SemVer points at a major. The blast radius is narrow:NotFoundErrorandInvalidRequestErrorshare theServerErrorparent, so anything rescuingResend::ErrororServerErroris unaffected.A major bump signals a rewrite. 1.0.0 was a genuine Contacts API redesign. The
Resend::Error::ClientErrorhierarchy fix is the change that warrants 2.0.0 — see the follow-up note below.The⚠️ changelog entry carries the migration instruction.
Follow-up, not in this PR
Resend::Error::ClientError(lib/resend/errors.rb:8) is referenced nowhere in the repo. Every 4xx code — 400, 401, 404, 422, 429 — subclassesServerErrorinstead. That inverted hierarchy is the root cause of #209:NotFoundErrorwas unreachable because the tree was never wired up.401 => InvalidRequestErrorhas the same problem, with no auth-specific class.Reparenting the 4xx classes is a real breaking change and belongs in 2.0.0.
Verification
Ran in a
ruby:3.4container, since the gem requires >= 3.2:bundle exec rspec— 336 examples, 0 failuresbundle exec rubocop— 39 files, no offensesResend::VERSIONresolves to1.7.0Before publishing
Put the⚠️ migration note in the GitHub release body. Auto-generated notes render #210 as
fix(errors): map 404 to NotFoundError by @Mohith26 in #210, which does not warn anyone upgrading for suppressions.Summary by cubic
Cut
resendv1.7.0 with the suppressions API, 404 -> NotFoundError mapping, and changelog compare-link fixes.New Features
Migration
Written for commit 9264ee5. Summary will update on new commits.