# open-telemetry/opentelemetry-js · Reposen Release & Migration Intelligence

> Lazy `@grpc/grpc-js` loading and credential redaction. Test in staging; do not deploy to prod. Migration: Low.

## Metadata
- **Repository URL**: https://github.com/open-telemetry/opentelemetry-js
- **Primary Package**: `@opentelemetry/api` (NPM)
- **Categories**: `ECOSYSTEM`, `BACKEND`
- **Latest Version**: `experimental/v0.301.2`
- **Semantic Status**: `WARNING`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/open-telemetry/opentelemetry-js/releases.atom

## The Human Context (Plain-English Pitch)
OpenTelemetry provides an open-source framework for collecting application traces, metrics, and telemetry data. It prevents vendor lock-in by standardizing how observability data is instrumented and exported to backends like Jaeger or Prometheus. This allows engineering teams to diagnose production latency and errors consistently across services.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Lazy `@grpc/grpc-js` loading and credential redaction. Test in staging; do not deploy to prod. Migration: Low.

## Breaking Changes & Required Actions
- Deferred loading of `@grpc/grpc-js` in `createServiceClientConstructor` avoids premature module initialization before `net` and `dns` monkey-patching hooks execute.
- Credential and sensitive query parameter redaction added to `url.full` spans across `@opentelemetry/instrumentation-fetch` and `@opentelemetry/instrumentation-xml-http-request`.
- Performance optimization in `@opentelemetry/otlp-transformer` utilizing native UTF-8 byte length computation during payload serialization.

## Migration Snippet
```ts
npm install @opentelemetry/exporter-trace-otlp-grpc@0.301.2 --save-exact
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **Node.js >=18** [`COMPATIBLE`]: Native utf8ByteLength optimization relies on standard Node.js runtime Buffer internals.
- **TypeScript >=5.0** [`COMPATIBLE`]: Fully typed declarations maintained across experimental package exports.
- **@grpc/grpc-js ^1.8** [`COMPATIBLE`]: Client constructor deferred to resolve monkey-patch race conditions during bootstrap.

## Zero-Noise Release Timeline
- **experimental/v0.301.2** (2026-11-12) [WARNING]: Lazy `@grpc/grpc-js` loading and credential redaction. Test in staging; do not deploy to prod. Migration: Low.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is open-telemetry/opentelemetry-js experimental/v0.301.2 safe to upgrade in production?
open-telemetry/opentelemetry-js experimental/v0.301.2 is classified as WARNING (PRERELEASE release). Lazy `@grpc/grpc-js` loading and credential redaction. Test in staging; do not deploy to prod. Migration: Low.

### What breaking changes or compatibility risks exist in open-telemetry/opentelemetry-js experimental/v0.301.2?
No breaking API changes or peer dependency conflicts are recorded for open-telemetry/opentelemetry-js experimental/v0.301.2 in the Reposen compatibility graph.

### What is the bundle size impact of @opentelemetry/api experimental/v0.301.2?
Measured bundle size telemetry is currently unavailable for @opentelemetry/api experimental/v0.301.2; verify build output locally before deploying.

### How do I upgrade @opentelemetry/api to experimental/v0.301.2?
Upgrade @opentelemetry/api to experimental/v0.301.2 by running "npm install @opentelemetry/api@experimental/v0.301.2" and applying the migration steps: npm install @opentelemetry/exporter-trace-otlp-grpc@0.301.2 --save-exact
