From 1a9483f8b6a4e0dc9b9c4eb71df5a15899abf430 Mon Sep 17 00:00:00 2001
From: "0xpolygon-changesets-release-bot[bot]"
 <267031455+0xpolygon-changesets-release-bot[bot]@users.noreply.github.com>
Date: Fri, 26 Jun 2026 13:21:43 +0000
Subject: [PATCH] release: version packages

---
 .changeset/maticjs-retry-transient-fetch.md | 5 -----
 packages/maticjs/CHANGELOG.md               | 6 ++++++
 packages/maticjs/package.json               | 2 +-
 3 files changed, 7 insertions(+), 6 deletions(-)
 delete mode 100644 .changeset/maticjs-retry-transient-fetch.md

diff --git a/.changeset/maticjs-retry-transient-fetch.md b/.changeset/maticjs-retry-transient-fetch.md
deleted file mode 100644
index 86fb5580..00000000
--- a/.changeset/maticjs-retry-transient-fetch.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@maticnetwork/maticjs': patch
----
-
-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 intermittent `Premature close` / `ECONNRESET` failures 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 shared `retryTransient` helper now used by both the metadata fetch and the receipt-proof RPC reads (replacing the bespoke inline retry in `getReceiptProof`); the shared classifier also recognises node-fetch's `Premature close`, which the old inline predicate missed.
diff --git a/packages/maticjs/CHANGELOG.md b/packages/maticjs/CHANGELOG.md
index a1ba3956..5b57fc14 100644
--- a/packages/maticjs/CHANGELOG.md
+++ b/packages/maticjs/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @maticnetwork/maticjs
 
+## 3.9.13
+
+### Patch Changes
+
+- [#481](https://github.com/0xPolygon/matic.js/pull/481) [`9dc06a2`](https://github.com/0xPolygon/matic.js/commit/9dc06a2399c6e1d9b85a0d426aafb764ff8a6960) Thanks [@MaximusHaximus](https://github.com/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 intermittent `Premature close` / `ECONNRESET` failures 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 shared `retryTransient` helper now used by both the metadata fetch and the receipt-proof RPC reads (replacing the bespoke inline retry in `getReceiptProof`); the shared classifier also recognises node-fetch's `Premature close`, which the old inline predicate missed.
+
 ## 3.9.12
 
 ### Patch Changes
diff --git a/packages/maticjs/package.json b/packages/maticjs/package.json
index 316841ed..87e8c703 100644
--- a/packages/maticjs/package.json
+++ b/packages/maticjs/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@maticnetwork/maticjs",
-  "version": "3.9.12",
+  "version": "3.9.13",
   "description": "Javascript developer library for interacting with Matic Network",
   "main": "dist/npm.export.js",
   "types": "dist/ts/index.d.ts",