Packages

@elastic/transport

9.6.1 · 18 Nov 2026Apache-2.02.3M / weekRepositoryHomepagenpmAtom feed

Upgrading @elastic/transport From 8.8.1 to 9.6.1

34 releases in betweennotes for 33

Other targets from 8.8.1Newest 8.x8.11.0
  1. 8.8.1yours
  2. 12 releases
  3. 9.0.0major
  4. 20 releases
  5. 9.6.1target
  6. 1 pre
3+
changes to make
0
advisories fixed
11+
new
38+
fixes

Counted from 33 of 34 release notes, and the breaking changes of 1 pre-release on the way to a major. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking9.0.0
  • Breaking9.0.0
  • Breaking9.0.0-alpha.1

Release by release

  1. 9.6.1

    18 Nov 202610 fixes
    • Fixed

      Validate per-request transport options (#422, fixes #405). Per-request maxRetries, maxResponseSize, and maxCompressedResponseSize now get the same checks as constructor options. Retry counts must be non-negative integers; invalid values throw ConfigurationError.

    • Fixed

      Honor per-request retryOnTimeout (#432, fixes #431). The per-request value now overrides the constructor value, like maxRetries and requestTimeout.

    • Fixed

      Reject already-aborted signals in HttpConnection (#443). A pre-aborted AbortSignal now rejects with RequestAbortedError without contacting the server, matching UndiciConnection.

    • Fixed

      Keep WeightedConnectionPool returning live connections (#445). getConnection could return null after markDead calls while live connections still existed.

  2. 9.6.0nothing new or fixed in the note

  3. 9.4.1

    2 Oct 20261 fix
    • Fixed

      Keep Undici connections alive on HEAD and DELETE-with-body requests (#420, fixes #419). By default, Undici marks the socket for reset on HEAD requests and on GET/DELETE requests that carry a body. That sends Connection: close and tears down the pooled socket after every such request. Elasticsearch handles both cases correctly, so the transport now passes reset: false to Undici. Pooled connections are reused, which avoids a new TCP/TLS handshake per request (for example, indices.exists).

  4. 9.4.0

    29 Jul 20262 new · 3 fixes
    • New

      Reject requests that exceed configurable maxPathLength

    • New

      Move OpenTelemetry tracing into a middleware; capture sanitized search queries as db.query.text #383

    • Fixed

      Prevent uncaught write EPIPE on peer close mid-request

    • Fixed

      Support path prefix in node URL

    • Fixed

      Strip credentials from OTel span attributes

  5. 9.3.7

    1 Jun 20261 fix
    • Fixed

      Mark timed-out nodes dead when retryOnTimeout is false

  6. 9.3.6

    20 May 20265 fixes
    • Fixed

      Use Buffer.concat for UTF-8 response body to prevent multi-byte character corruption

    • Fixed

      Prevent false NoLivingConnectionsError in WeightedConnectionPool

    • Fixed

      Prevent ConnectionError with empty message

    • Fixed

      Ensure Error.cause propagates

    • Fixed

      Use correct content-type on empty requests

  7. 9.3.3 – 9.3.53 releases, nothing new or fixed in the notes

  8. 9.3.2

    5 Feb 20261 fix
    • Fixed

      Hot fix to properly support ESM/CommonJS imports on Windows

1 other line we could not sort, mostly version bumps
  • Pin caFingerprint to the matching certificate (#426). A fingerprint match used to accept the connection. The matching certificate is now the only trust anchor, and signature, expiry, and hostname checks stay on. A function agent cannot be combined with caFingerprint.

    9.6.0

1 internal line (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.