fix(deps): update dependency @upyo/core to v0.5.0#1723
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1723 +/- ##
=======================================
Coverage 45.53% 45.53%
=======================================
Files 159 159
Lines 5749 5749
Branches 927 927
=======================================
Hits 2618 2618
Misses 3131 3131 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
This PR contains the following updates:
0.4.0→0.5.0Release Notes
dahlia/upyo (@upyo/core)
v0.5.0Compare Source
Released on July 1, 2026.
@upyo/core
Added structured delivery error metadata to failed
Receiptvalues.Failed receipts still include
errorMessagesfor existing code, and maynow also include
errors,retryable,provider,attempts, andtimestampfields for programmatic error handling. Structured errors mayalso include provider-specific
providerDetailswhen a transport exposesthem. [#25, #27]
Receipt,ReceiptError, andTransportare now generic over thetransport provider id, and
Transportimplementations expose a stableidfield soprovidermetadata can be type-checked.ReceiptErrorinterface.ReceiptErrorCategorytype.ReceiptErrorClassificationinterface.CreateReceiptErrorOptionsinterface.CreateFailedReceiptOptionsinterface.classifyHttpStatus()function.classifyReceiptError()function.createReceiptError()function.createFailedReceipt()function.parseRetryAfter()function.@upyo/jmap
JmapTransportto return structured failure receipts withprovider ids, retryability, HTTP status codes, retry delay metadata from
Retry-After, and attempt counts where available. [#25, #27]@upyo/lettermint
Added Lettermint transport. [#22, #23]
LettermintTransportclass.LettermintConfiginterface.ResolvedLettermintConfigtype.LettermintSettingsinterface.LettermintApiErrorclass.LettermintBatchResponsetype.LettermintErrorinterface.LettermintResponseinterface.LettermintStatustype.inline images, routes, tags, metadata, and tracking settings.
@upyo/mailgun
MailgunTransportto return structured failure receipts withprovider ids, retryability, HTTP status codes, retry delay metadata from
Retry-After, and attempt counts where available. [#25, #27]@upyo/plunk
PlunkTransportto return structured failure receipts withprovider ids, retryability, HTTP status codes, retry delay metadata from
Retry-After, and attempt counts where available. [#25, #27]@upyo/resend
ResendTransportto return structured failure receipts withprovider ids, retryability, HTTP status codes, retry delay metadata from
Retry-After, and attempt counts where available. Batch item failuresnow include structured error metadata as well. [#25, #27]
@upyo/sendgrid
SendGridTransportto return structured failure receipts withprovider ids, retryability, HTTP status codes, retry delay metadata from
Retry-After, and attempt counts where available. [#25, #27]@upyo/ses
SesTransportto return structured failure receipts with providerids, retryability, HTTP status codes, retry delay metadata from
Retry-After, and attempt counts where available. [#25, #27]@upyo/smtp
Updated
SmtpTransportto return structured failure receipts withprovider ids, retryability, attempt counts, and classified network,
timeout, authentication, and rejection errors. [#25, #27]
Added OAuth 2.0 authentication support to the SMTP transport, using the
SASL XOAUTH2 and OAUTHBEARER (RFC 7628) mechanisms. This enables
authentication with providers such as Gmail and Outlook that require OAuth
2.0 instead of passwords. [#19, #24]
SmtpAuthis now a discriminated union ofSmtpUserPassAuth(username/password, as before) and the OAuth 2.0 variants. Existing
{ user, pass }configurations continue to work unchanged.SmtpOAuth2Auth,SmtpOAuth2TokenAuth, andSmtpOAuth2RefreshAuthinterfaces, and theSmtpUserPassAuthinterface.
OAuth2TokenProvidertype. TheaccessTokenfield acceptseither a static token string or a callback returning a fresh token,
which can integrate an external OAuth client (e.g.,
google-auth-libraryormsal-node) for transparent refresh.refresh_tokengrant flow(
SmtpOAuth2RefreshAuth): provideclientId,refreshToken, andtokenEndpoint, and the transport exchanges them for an access token,caching it across pooled connections until shortly before it expires.
SmtpAuthErrorclass, thrown on OAuth token acquisition andSASL authentication failures.
Changed
SmtpTransport.send()andSmtpTransport.sendMany()to reportconnection and authentication setup failures as a failed
Receiptinsteadof throwing. Previously, a failure to connect or authenticate (e.g., an
invalid host, a refused connection, or rejected credentials) rejected the
returned promise, which was inconsistent with message-level failures (such
as a rejected recipient) that were already reported as a failed
Receipt.Now all delivery failures—including setup failures—are reported uniformly
as a failed
Receipt. Cancellation viaAbortSignalcontinues to reject.[#19, #24]
@upyo/pool
PoolTransportto preserve child transport provider ids inaggregated structured errors. The pool itself reports failed aggregate
receipts with the
"pool"provider id, while child errors keep theunderlying transport ids as a type-safe union. [#25, #27]
@upyo/retry
RetryTransportwraps any existing transport andretries transient failed receipts or thrown transient errors using
configurable exponential backoff, jitter,
Retry-Aftermetadata, andsendMany()launch throttling. Use it when one provider should absorbtemporary rate limits, server errors, and network failures before handing
a failure back to application code. [#26, #28]
@upyo/opentelemetry
hyphen spelling:
rate-limit,service-unavailable, andserver-error.OpenTelemetry metrics now prefer structured receipt categories when a
wrapped transport returns them, then fall back to the configured error
classifier. [#25, #27]
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.