changesets: Release / Deploy#482
Merged
Merged
Conversation
MaximusHaximus
approved these changes
Jun 26, 2026
MaximusHaximus
left a comment
MaximusHaximus
left a comment
Contributor
There was a problem hiding this comment.
Release of 3.9.13 — consumes the #481 changeset (retry transient ABI/metadata fetch failures incl. node-fetch 'Premature close'). CI green; approving per release flow.
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
1 participant
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@maticnetwork/maticjs@3.9.13
Patch Changes
9dc06a2Thanks @MaximusHaximus! - Retry transient network failures when fetching network/ABI metadata. The config-store fetch (ABIManager.init→HttpRequest) now retries connection-level errors with exponential backoff, fixing intermittentPremature close/ECONNRESETfailures from stale keep-alive sockets (Node 19+ keeps HTTP connections alive by default) that previously surfaced as a misleading "network mainnet - v1 is not supported". The retry/backoff and transient-error classification are extracted into a sharedretryTransienthelper now used by both the metadata fetch and the receipt-proof RPC reads (replacing the bespoke inline retry ingetReceiptProof); the shared classifier also recognises node-fetch'sPremature close, which the old inline predicate missed.