NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #2507 most downloaded on npm
Provides low-level interfaces and helper methods for tracing in Azure SDK
Latest stable
1.4.0
Last release 4 months ago
13 Jul 2026
Ships unpredictably
gaps range from 8 days to 4 months
Nearly every release is documented
notes for 9 of 9 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
534 releases · first in 2019
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
Revert TypeScript output target to ES2017.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Add top-level browser field to package.json as fallback for legacy bundlers that do not support the exports field.
browser field to package.json as fallback for legacy bundlers that do not support the exports field.Nothing published for this version
Initial stable release of the Azure Device Update for IoT Hub client library for JavaScript, generated from TypeSpec.
2026-06-01, including the new optional
downloadSecurity property on Deployment so callers can choose the protocol
the device should use when downloading update payload (defaults to "https").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
Minor improvements to the typing of updatedOptions when calling startSpan.
updatedOptions when calling startSpan.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
This is the first stable release of the @azure/arm-connectedcache package. It introduces a new SDK generation with layered APIs, smaller bundles, and
This is the first stable release of the @azure/arm-connectedcache package. It introduces a new SDK generation with layered APIs, smaller bundles, and improved ergonomics. For more details, see the https://aka.ms/azsdk/js/sdk/quickstart.
This is the first stable version with the package of @azure/arm-weightsandbiases.
This is the first stable release of the @azure/arm-cloudhealth package. It introduces a new SDK generation with layered APIs, smaller bundles, and improved ergonomics. For more details, see the https://aka.ms/azsdk/js/sdk/quickstart.
This is the first stable release of the @azure/arm-edgezones package. It introduces a new SDK generation with layered APIs, smaller bundles, and improved ergonomics. For more details, see the https://aka.ms/azsdk/js/sdk/quickstart.
This release migrates the package to the @azure/ai-translation-document name and a new client design. It replaces the previous @azure-rest/ai-translation-document REST-level client (RLC) package.
2026-03-01 service API version.deploymentName to TargetInput and DocumentStatus to support translating with a custom translation model.deploymentName parameter to single document translation.translateTextWithinImage on batch and single document translation, and image-scan fields (imageCharacterDetected, imageCharged, totalImageScansSucceeded, totalImageScansFailed) on DocumentStatus.@azure-rest/ai-translation-document to @azure/ai-translation-document.client.path(...).post(...)) has been replaced with a modeled client surface exposing DocumentTranslationClient and SingleDocumentTranslationClient. See the README for migration examples.Install the new package: replace @azure-rest/ai-translation-document with @azure/ai-translation-document.
Create the client: the default export factory is replaced by named clients.
- import DocumentTranslator from "@azure-rest/ai-translation-document";
- const client = DocumentTranslator(endpoint, credential);
+ import { DocumentTranslationClient } from "@azure/ai-translation-document";
+ const client = new DocumentTranslationClient(endpoint, credential);
Call operations: replace the path(...).method() pattern with typed methods.
- await client.path("/document/batches").post({ body: { inputs } });
+ await client.startTranslation({ inputs });
Single document translation: use SingleDocumentTranslationClient.
- import DocumentTranslator from "@azure-rest/ai-translation-document";
- const client = DocumentTranslator(endpoint, credential);
- await client.path("/document:translate").post({ ... });
+ import { SingleDocumentTranslationClient } from "@azure/ai-translation-document";
+ const client = new SingleDocumentTranslationClient(endpoint, credential);
+ await client.translate(targetLanguage, content);
Responses: results are returned as typed objects and errors are thrown as RestError, instead of checking response.status on a raw HTTP response.
WorkspaceClient (conversations, investigations, tasks, tools) and BookshelfClient (knowledge bases).This release marks the GA release of our @azure/core-tracing libraries and is unchanged from preview.14
@azure/core-tracing has been rewritten in order to provide cleaner abstractions for client libraries as well as remove @opentelemetry/api as a direct
createSpanFunction has been removed and replaced with a stateful TracingClient which can be created using the createTracingClient function.TracingClient introduces a new API for creating tracing spans. Use TracingClient#withSpan to wrap an invocation in a span, ensuring the span is ended and exceptions are captured.TracingClient also provides the lower-level APIs necessary to start a span without making it active, create request headers, serialize traceparent header, and wrapping a callback with an active context.Added support for disabling distributed tracing using the AZURE_TRACING_DISABLED environment variable.
TestTracer and TestSpan from public API and into @azure/test-utils. PR #16315
TestTracer and TestSpan are intended for test support when used by other Azure packages and not intended for use by end users.setTracer, @azure/core-tracing will now rely on the trace API to fetch a tracer from the global tracer provider. PR #16347
setTracer, please use trace.setGlobalTracerProvider(provider) instead as described in the OpenTelemetry documentation.NoOpTracer and NoOpSpan from the public API. Please use trace.wrapSpanContext(INVALID_SPAN_CONTEXT) from @opentelemetry/api instead. PR #16315Update @opentelemetry/api to version 1.0.0 PR #15883
@opentelemetry/api to version 1.0.0 PR #15883
OpenCensusSpanWrapper and OpenCensusTracerWrapper from the public API. Customers using these wrappers should migrate to using OpenTelemetry directly. PR #15770@azure/core-tracing to version 1.0.0-preview.12. This brings core-tracing up to date with @opentelemetry/api@1.0.0.
Span#context was renamed to Span#spanContext. This change is supported in @azure/core-http@1.2.7.Update @azure/core-tracing to version 1.0.0-preview.11. This brings core-tracing up to date with @opentelemetry/api@1.0.0-rc.0. There are two scenario
OperationOptions.tracingOptions.spanOptions.parentSpan property. This has been
changed so that you now specify a parent Context using the OperationOptions.tracingOptions.tracingContext property instead.CanonicalCode. Instead, it's now SpanStatusCode, which also has a smaller range of values.Internal improvements to make future opentelemetry updates simpler.
One column per quarter.