chore(deps): update dependency postmark to v5 - #3937
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/postmark-5.x
branch
from
July 20, 2026 18:56
f8a5bb3 to
1af5b9f
Compare
renovate
Bot
force-pushed
the
renovate/postmark-5.x
branch
from
July 23, 2026 14:41
1af5b9f to
8fa84bd
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.
This PR contains the following updates:
4.0.7→5.1.0Release Notes
ActiveCampaign/postmark.js (postmark)
v5.1.0Compare Source
ServerClient.sendBulkEmail()— send a bulk email (POST /email/bulk)ServerClient.getBulkEmailStatus()— poll a bulk request's status (GET /email/bulk/{bulk-request-id})BulkEmailRequest,BulkEmailMessage,BulkEmailSendingResponse,BulkEmailStatusResponse, and theBulkEmailStatusenum, withBulkEmailRequest/BulkEmailMessageexposed as top-level exportsv5.0.0Compare Source
Migrated the HTTP client from axios to the native Fetch API, making the SDK dependency-free.
This is a major release; the migration introduces five breaking changes, detailed below.
Breaking changes
HTTP_PROXY/HTTPS_PROXY/NO_PROXY) are no longer honored automatically. axios read them viaproxy-from-env, but Node's built-in fetch (undici) does not. To route requests through a proxy, pass a custom fetch via the newfetchclient option (e.g. bound to an undiciProxyAgentdispatcher) — see the README "Proxies / custom fetch" section.2xxresponse body now resolves to{}instead of the empty string""that axios surfaced.client.httpClient.clientis no longer an axios instance — it is now afetchfunction. Code that reached into it to add axios interceptors, setdefaults, or attach an axios adapter/proxy will no longer work; use the newfetchclient option for transport customization instead.timeoutsemantics changed. With axiostimeoutwas a response/inactivity timeout; it is now mapped toAbortSignal.timeout(), which is a total deadline for the entire request. Slow-but-progressing responses that previously completed may now abort once the total duration exceeds the configuredtimeout.Other changes
axiosdependency (resolves CVE exposure andurl.parse()deprecation warnings, and restores compatibility with Edge/Workers runtimes)fetchclient option, allowing a custom fetch implementation to be supplied for proxy support, testing, or other transport customizationConfiguration
📅 Schedule: (in timezone UTC)
* 0-3 * * 1)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.