NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #2679 most downloaded on npm
Isomorphic client library for making HTTP requests in node.js and browser.
Latest stable
1.25.1
Last release 14 days ago
08 Nov 2026
Ships unpredictably
gaps range from 8 days to 4 months
Nearly every release is documented
notes for 51 of 52 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
537 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
[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
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Update engines to "node": ">=22.0.0". Please refer to our support policy for more information on our supported Node.js versions.
engines to "node": ">=22.0.0". Please refer to our support policy for more information on our supported Node.js versions.Code | Docs
Support: Active
Core - Client - Core Utils
@azure/core-util
Use and export type aliases on public API surface PR #38205
Nothing published for this version
Nothing published for this version
Nothing published for this version
Added allowCrossOriginRedirects option to RedirectPolicyOptions. #37384
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
Fix invalid format of "User-Agent" header value Issue #36383
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
Upgrade @azure/* dependencies to latest versions.
@azure/* dependencies to latest versions.One column per quarter.