NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #1306 most downloaded on npm
Provides a way to make requests
Last release 1 months ago
03 Sep 2026
Ships on a steady schedule
a new release about every 1 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
2 versions withdrawn
withdrawn after publishing
3 years old
118 releases · first in 2023
One column per quarter.
1d85108 : Clear the HTTP/2 session timeout before destroying a session. Node keeps a destroyed Http2Session reachable until its pending setTimeout fir
Http2Session reachable until its pending setTimeout fires, so with the default 300 s timer on isolated sessions every completed request was retained for 5 minutes.bb68484 : destroy isolated http2 session and manage timeout
a825452 : switch for-in loops to guarded
99c3f91: Restore npm provenance attestations. No functional changes.
d774f8d: chore: build packages with typescript 7. Packages continue to be compatible with TypeScript 3.4 through 7.0 in consumer applications.
cf69285: use the client logger as a fallback when the request handler has no logger configured, while preserving an explicitly configured handler logg
ec9b4b2: chore: update builds to use typescript 6. This should not affect consumers, who may continue to use TypeScript 3.4 through 7.0 as of this ver
### Patch Changes - Updated dependencies [fcf1366] - @smithy/core@3.31.1
### Patch Changes - Updated dependencies [a14bb71] - @smithy/core@3.31.0
### Patch Changes - Updated dependencies [54040ef] - Updated dependencies [155bb56] - @smithy/core@3.30.0
### Patch Changes - Updated dependencies [d6e6f8b] - @smithy/core@3.29.8
### Patch Changes - Updated dependencies [44b21e6] - @smithy/core@3.29.7
### Patch Changes - Updated dependencies [3248fbd] - @smithy/core@3.29.6
### Patch Changes - Updated dependencies [b44cb0a] - @smithy/core@3.29.5
### Patch Changes - Updated dependencies [5fca3a0] - @smithy/core@3.29.4
### Patch Changes - Updated dependencies [a97abc3] - @smithy/types@4.16.1 - @smithy/core@3.29.3
273e480: types updates for isolatedModules=true
### Patch Changes - Updated dependencies [1fac409] - @smithy/core@3.29.1
### Patch Changes - Updated dependencies [12bceb2] - Updated dependencies [4395dad] - @smithy/core@3.29.0 - @smithy/types@4.15.1
### Patch Changes - Updated dependencies [d366537] - Updated dependencies [c0d7f5d] - @smithy/core@3.28.0
c9575e1: use streamCollector from core/serde
99c3f91: Restore npm provenance attestations. No functional changes.
d774f8d: chore: build packages with typescript 7. Packages continue to be compatible with TypeScript 3.4 through 7.0 in consumer applications.
ec9b4b2: chore: update builds to use typescript 6. This should not affect consumers, who may continue to use TypeScript 3.4 through 7.0 as of this ver
1e5bdd3: Update author URL in package.json to be more specific
9ea5ce5: import node:http,https,http2 using default export object (writable)
### Patch Changes - Updated dependencies [776bc52] - Updated dependencies [5b92a54] - @smithy/types@4.14.3 - @smithy/core@3.24.6
### Patch Changes - Updated dependencies [721fbed] - @smithy/core@3.24.5
### Patch Changes - Updated dependencies [9eaa5c6] - @smithy/core@3.24.4
### Patch Changes - Updated dependencies [cf00244] - @smithy/types@4.14.2 - @smithy/core@3.24.3
99c3f91: Restore npm provenance attestations. No functional changes.
d774f8d: chore: build packages with typescript 7. Packages continue to be compatible with TypeScript 3.4 through 7.0 in consumer applications.
ec9b4b2: chore: update builds to use typescript 6. This should not affect consumers, who may continue to use TypeScript 3.4 through 7.0 as of this ver
d774f8d: chore: build packages with typescript 7. Packages continue to be compatible with TypeScript 3.4 through 7.0 in consumer applications.
ec9b4b2: chore: update builds to use typescript 6. This should not affect consumers, who may continue to use TypeScript 3.4 through 7.0 as of this ver
131fce4: add eventStream indicator signal for NodeHttp2ConnectionManager so it does not reuse connections for event streams
99c3f91: Restore npm provenance attestations. No functional changes.
d774f8d: chore: build packages with typescript 7. Packages continue to be compatible with TypeScript 3.4 through 7.0 in consumer applications.
@smithy/abort-controller to devDepsec9b4b2: chore: update builds to use typescript 6. This should not affect consumers, who may continue to use TypeScript 3.4 through 7.0 as of this ver
### Patch Changes - Updated dependencies [fcf1366] - @smithy/core@3.31.1
dab22f1: fix: do not return caller's Error directly from buildAbortError
Always create a new mutable Error when the abort reason is an Error, preserving the original via .cause. Fixes TypeError when retry middleware tries to set $metadata on a frozen/sealed abort reason.
### Patch Changes - Updated dependencies [a14bb71] - @smithy/core@3.31.0
a4d95e6: Set downlevel types to be used in typescript@'<4.5'
9bf9ae2: fix: reject aborted requests with AbortSignal.reason instead of a generic Error
@smithy/abort-controller@4.2.10
03c3dc8: update for rollup build externalLiveBindings=false
f6f0de9: write request.end() with no arg if empty buffer
3ee4e66: Use configured logger when provided.
@smithy/querystring-builder@4.2.8
@smithy/querystring-builder@4.2.7
@smithy/querystring-builder@4.2.6
@smithy/querystring-builder@4.2.5
df00095: skip body write delay when http Agent is externally owned
344d06a: shfit http1 calls with expect 100-continue header to isolated http Agents
99c3f91: Restore npm provenance attestations. No functional changes.
d774f8d: chore: build packages with typescript 7. Packages continue to be compatible with TypeScript 3.4 through 7.0 in consumer applications.
ec9b4b2: chore: update builds to use typescript 6. This should not affect consumers, who may continue to use TypeScript 3.4 through 7.0 as of this ver
45ee67f: update dist-cjs generation to use rollup
@smithy/querystring-builder@4.1.1
64cda93: set sideEffects bundler metadata
@smithy/querystring-builder@4.0.5
Your coding agent can read these notes before it upgrades. Set up the MCP server →