NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3158 most downloaded on npm
Isomorphic client library for making HTTP requests in node.js and browser.
Latest stable
0.3.10
Last release 13 days ago
07 Nov 2026
Release timing varies
gaps range from 8 days to 2 months
Nearly every release is documented
notes for 16 of 16 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
375 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[ai-projects] Fix telephony customization drift from 47968
[ai-projects] Fix telephony customization drift from 47968 (#40673)
### Packages impacted by this PR
`@azure/ai-projects` (`sdk/ai/ai-projects`) customization tooling,
regression fixtures, and post-emitter guidance only. No checked-in
generated SDK, source API, package version, dependency, or changelog
changes.
### Issues associated with this PR
SDK Validation - JS failures for Azure/azure-rest-api-specs#47968:
https://dev.azure.com/azure-sdk/29ec6040-b234-4e31-b139-33dc4287b756/_build/results?buildId=7043739
### Describe the problem that is addressed by this PR
The strict customization resolver needs to reconcile JavaScript-only
client-name decorators for telephony campaign schedules, retry policy,
and endpoint address models. It also needs to preserve maintained
telephony behavior while the emitter changes request shape, wrappers,
and discriminator representation.
This PR:
- follows the seven approved telephony declaration and converter renames
only when the old and new emitted ASTs are structurally equivalent and
the customization retains the baseline symbol;
- safely merges the `sip` provider addition while retaining the existing
`teams_phone_extensibility` and `twilio` request variants;
- ports emitted parameter-only changes through customized tracing
wrappers when the wrapper still contains the one exact baseline
operation delegate;
- adopts the equivalent `FileSearchToolFiltersValue` alias
representation without replacing unrelated filter customizations;
- corrects the generated `subProtocol`/`sub_protocol` discriminator
spelling in the voice-agent union serializer; and
- documents and regression-tests the supported policies.
The prior Agent Insight Monitor beta-to-root repair in #40669 now
removes the seven monitor relocation diagnostics from this spec
generation. Combined with this change, the exact
Azure/azure-rest-api-specs#47968 emission completes strict customization
and source compilation.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
Manual recovery or broad legacy-model retention could bypass the strict
pipeline, silently keep obsolete generated names, or drop emitted
changes. This PR instead adds fail-closed policies: explicit approved
rename pairs require equivalent emitted declaration/converter shapes,
the provider-union exception requires the exact prior two values plus
`sip`, and tracing-wrapper support requires one exact baseline delegate
and unchanged forwarding. Other union replacements, ambiguous symbols,
altered wrappers, and unsupported concurrent edits continue to fail.
### Are there test cases added in this PR? _(If not, why?)_
Yes. Focused fixtures cover accepted/rejected telephony name mappings,
retained provider variants plus `sip`, altered provider replacements,
equivalent filter aliases, snake-case voice discriminator dispatch, and
traced classic wrappers with parameter renames or changed forwarding.
Validation:
- `npm run test:customize` - passed: 242 tests, 241 passed, 1 skipped.
- `npm run customize` - passed on the unchanged package baseline.
- Exact 47968 emission in an isolated clone: `npm run customize` -
passed strict guards for 32 changed generated files and 149 source
files.
- Exact 47968 emission: `npx tsc -p tsconfig.src.json --noEmit` -
passed.
- `pnpm turbo build --filter=@azure/ai-projects... --token 1` from the
repository root - passed: 26 successful tasks.
- `npm run lint` - passed with 0 errors and 27 existing warnings.
- `pnpm exec prettier --check <all changed files>` and `git diff
--check` - passed.
The exact TypeSpec emission used the `47968` head
`38a738fe0b707464ca1f6b8588a26eb2d3256ece` and the compatible
`@azure-tools/openai-typespec` 1.34.1 dependency already required by the
pipeline-era Foundry spec.
### Provide a list of related PRs _(if any)_
- Azure/azure-rest-api-specs#47968
- #40669
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
Not applicable. This is a customization-tooling repair, not an SDK
release request.
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR need any fixes in the SDK Generator? _(If so, create
an Issue in the
[typespec-azure](https://github.com/Azure/typespec-azure) repository and
link it here)_
- [ ] Added a changelog (if necessary)
The impacted package is listed in this PR. No SDK Generator fix is
requested; the resolved `sub_protocol` access is a local post-emitter
compatibility correction for current emitted input. No package changelog
or version update is needed for this tooling-only change.
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Copilot-Session: ae111d31-bcb8-4e15-a828-a37821098cbb
Expect: 100-continue support to the Node.js HTTP/1 transport. Browser and React Native transports reject requests with an Expect header. #40251azure-deprecating response header is now included in the default set of headers logged without redaction. See Azure API Guidelines: Deprecating Behavior Notification for more information. #39420workerd export condition so Cloudflare Workers using nodejs_compat resolve the Node-compatible build, including Node HTTP and proxy support, instead of the browser build. Issue #37345ArrayBuffer, DataView, or typed arrays other than Uint8Array are now sent as their original bytes instead of being JSON serialized. #40382content-type and accept entries of the headers request option without regard to how the header name is capitalized. Only the all lower case spellings were found before, so headers: { "Content-Type": "application/xml" } and headers: { "Accept": "text/plain" } were replaced by the default application/json. Both entries are now read back from the headers that will be sent, so the same value decides the header and how the body is encoded: a header name given under two spellings resolves to the last one in the object, a content-type value that is not a string, such as a number, is used as its string form rather than ignored, and a padded value selects the encoding of its trimmed form. #39791http-proxy-agent dependency to version 9.1.0. Issue #37669https-proxy-agent dependency to version 9.1.0. #40259[core] prepare September releases
[core] prepare September releases (#39854)
Prepare the changelogs for the September 3, 2026 core package releases.
Copilot-Session: d4cfeed9-f7c7-4cd9-8e2e-8a7c4e8285bf
NodeHttpClient request timeouts now remain active while buffered response bodies are being read. Issue #39519FetchHttpClient now surfaces the system error code (such as ECONNRESET or ETIMEDOUT) carried by the cause of a failed fetch() call on the resulting RestError, so that systemErrorRetryPolicy retries transient network failures instead of rethrowing them immediately. Issue #39703Added an optional internal property to ClientOptions for getClient, carrying a noDefaultAcceptHeader flag (defaults to false). When set to true, the c
internal property to ClientOptions for getClient, carrying a noDefaultAcceptHeader flag (defaults to false). When set to true, the client no longer adds a default Accept: application/json request header to operations that do not otherwise specify one, allowing operations that expect no response body to omit the Accept header. This option is intended for use by generated clients. PR #39291proxyPolicy no longer throws on platforms where proxies are not supported (such as browsers and React Native). Instead, it returns a no-op policy that forwards requests unchanged, and getDefaultProxySettings returns undefined PR #39084logPolicy now redacts non-allowlisted response header values when verbose logging is enabled, instead of logging them in plaintext.
logPolicy now redacts non-allowlisted response header values when verbose logging is enabled, instead of logging them in plaintext.randomUUID polyfill for Node.js and browsers, relying on globalThis.crypto.randomUUID() which is available on those platforms. React Native keeps a Math.random() based fallback since its JS engines do not provide crypto.randomUUID().engines to "node": ">=22.0.0". Please refer to our support policy for more information on our supported Node.js versions.Fix an issue in NodeHttpClient where we incorrectly send the whole backing buffer when request body is an ArrayBufferView. PR #38718
NodeHttpClient where we incorrectly send the whole backing buffer when request body is an ArrayBufferView. PR #38718createHttpHeaders now strips CR (\r) and LF (\n) characters from header values to prevent obs-fold (line folding) sequences, as required by RFC 7230 §3.2.4. PR #38744Request headers are no longer forwarded to the proxy server as additional headers when establishing HTTPS CONNECT tunnels; headers on proxied HTTP(S)
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Added allowCrossOriginRedirects option to RedirectPolicyOptions. #37384
allowCrossOriginRedirects option to RedirectPolicyOptions. #37384Blob type for request body. (#37300, #37424)allowCrossOriginRedirects to true to restore the previous behavior. #37384Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.