chore(release): 1.4.0

[Jackson Weber (JacksonWeber)]

Release 1.4.0

Align Azure Monitor exporter and Azure SDK instrumentation with @azure/monitor-opentelemetry 1.20.0, deduplicate the exporter's OpenTelemetry dependencies, and roll up release notes since 1.3.0.

Release metadata

• Bump package.json and MICROSOFT_OPENTELEMETRY_VERSION to 1.4.0.
• Roll unreleased changes into the 2026-09-08 release notes, including A365 durable delivery, LangChain GenAI attributes, AKS instrumentation, telemetry fixes, and CI/dependency maintenance.
• Refresh the root lockfile and the samples' local-package metadata.

Azure Monitor / OpenTelemetry alignment

Use the published @azure/monitor-opentelemetry@1.20.0 and its @azure/monitor-opentelemetry-exporter@1.0.0-beta.45 dependency as the compatibility baseline.

Dependency	Before	Release
@azure/monitor-opentelemetry-exporter minimum	1.0.0-beta.44	1.0.0-beta.45
@azure/opentelemetry-instrumentation-azure-sdk	^1.0.0	^1.1.0-beta.1
OpenTelemetry core/SDK	2.10.0 / 0.221.0	Retained: already matches Azure Monitor
OpenTelemetry API / semantic conventions	1.9.1 / 1.43.0	Retained: already matches Azure Monitor

All shared direct OpenTelemetry dependency ranges match both published Azure Monitor packages. Updating the exporter removes its nested OpenTelemetry core/resources 2.9.0 and logs 0.220.0 copies, allowing it to use the distro's 2.10.0 / 0.221.0 packages.

The exporter's npm latest tag still points to beta.32; this deliberately uses the newer beta.45 release referenced by Azure Monitor 1.20.0 and the exporter's beta tag. The existing beta-only version range remains in place.

Validation

• Build, ESM import regression, and built-package OTLP integration passed on Node 24.15.0.
• Dependency alignment, release version consistency, lockfile metadata, and changed-file formatting checks passed.
• Test run: 1,119 passed, 5 todo, with three timing failures in A365 replay and browser-loader tests. Rerunning both affected files in isolation passed all 136 tests without code changes.

[Copilot]

🟡 Changes recommended

The release bump appears incomplete/inconsistent for samples (a hard-pinned 1.3.0 sample remains, and sample Node engine constraints don’t match the distro’s Node >=22 requirement).

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR prepares the @microsoft/opentelemetry JavaScript distro for the 1.4.0 release by bumping the distro version, aligning Azure Monitor exporter / Azure SDK instrumentation dependency ranges with @azure/monitor-opentelemetry 1.20.0, and updating the changelog for the release.

Changes:

• Bump distro version from 1.3.0 to 1.4.0 (package metadata + exported runtime constant).
• Update Azure Monitor exporter and Azure SDK instrumentation dependency ranges (and lockfiles) to the new aligned versions.
• Add the 1.4.0 release section to CHANGELOG.md.

File summaries

File	Description
src/types.ts	Updates exported distro version constant to 1.4.0.
package.json	Bumps package version to 1.4.0 and updates Azure Monitor-related dependency ranges.
package-lock.json	Updates lockfile to reflect version bump and transitive dependency changes from the Azure Monitor exporter update.
samples/package-lock.json	Updates sample lockfile to reflect the new distro version and Azure Monitor dependency alignment.
CHANGELOG.md	Adds 1.4.0 release notes and dependency-alignment notes.

Review details

Files not reviewed (1)

• samples/package-lock.json: Generated file

• Files reviewed: 3/5 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.