1.26.0

🚀 (Enhancement)

• feat: include instrumentation scope info in console span and log record exporters #4848 @blumamir
• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
  • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

🐛 (Bug Fix)

• fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @trentm
• deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @lforst
• fix(instrumentation): Fix optional property types #4833 @alecmev
• fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829

🏠 (Internal)

• refactor: Simplify the code for the getEnv function #4799 @danstarns
• refactor: remove "export *" in favor of explicit named exports #4880 @robbkidd
  • Packages updated:
    • opentelemetry-context-zone
    • opentelemetry-core
    • opentelemetry-exporter-jaeger
    • opentelemetry-exporter-zipkin
    • opentelemetry-propagator-b3
    • opentelemetry-propagator-jaeger
    • opentelemetry-sdk-trace-base
    • opentelemetry-sdk-trace-node
    • opentelemetry-sdk-trace-web
    • propagator-aws-xray
    • sdk-metrics
• deps(sdk-metrics): remove unused lodash.merge dependency #4905 @pichlermarc

1.27.0

• Version bump only
• Note: This package will now be versioned according to the version of semantic conventions being provided.

0.53.0

💥 Breaking Change

• fix(instrumentation)!:remove unused description property from interface #4847 @blumamir
• feat(exporter--otlp-)!: use transport interface in node.js exporters #4743 @pichlermarc
  • (user-facing) headers was intended for internal use has been removed from all exporters
  • (user-facing) compression was intended for internal use and has been removed from all exporters
  • (user-facing) hostname was intended for use in tests and is not used by any exporters, it will be removed in a future release
• fix(exporter--otlp-)!: ensure User-Agent header cannot be overwritten by the user #4743 @pichlermarc
  • allowing overrides of the User-Agent header was not specification compliant.
• feat(exporter--otlp)!: remove environment-variable specific code from browser exporters
  • (user-facing) removes the ability to configure browser exporters by using process.env polyfills
• feat(sdk-node)!: Automatically configure logs exporter #4740
• feat(exporter--otlp-)!: use transport interface in browser exporters #4895 @pichlermarc
  • (user-facing) protected headers property was intended for internal use has been removed from all exporters

🚀 (Enhancement)

• feat(otlp-transformer): Do not limit @opentelemetry/api upper range peerDependency #4816 @mydea
• feat(instrumentation-http): Allow to opt-out of instrumenting incoming/outgoing requests #4643 @mydea
• feat(sampler-jaeger-remote): added support of jaeger-remote-sampler according to this spec #4534 @legalimpurity

🐛 (Bug Fix)

• fix(instrumentation): ensure .setConfig() results in config.enabled defaulting to true #4941 @trentm
• fix(instrumentation-http): Ensure instrumentation of http.get and https.get work when used in ESM code #4857 @trentm
• fix(api-logs): align AnyValue to spec #4893 @blumamir
• fix(instrumentation): remove diag.debug() message for instrumentations that do not patch modules #4925 @trentm

🏠 (Internal)

• refactor: Simplify the code for the getEnv function #4799 @danstarns
• refactor: remove "export *" in favor of explicit named exports #4880 @robbkidd
  • Packages updated:
    • api-events
    • api-logs
    • opentelemetry-browser-detector
    • opentelemetry-exporter-prometheus
    • opentelemetry-instrumentation-fetch
    • opentelemetry-instrumentation-http
    • opentelemetry-instrumentation-xml-http-request
    • opentelemetry-instrumentation

@opentelemetry/[email protected]

Note: This package will now be versioned according to the version of semantic conventions being provided.

🚀 (Enhancement)

• feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @dyladan
  • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
  • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.

1.25.1

📚 (Refine Doc)

• refactor(examples): added usage of @opentelemetry/semantic-conventions and @opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @Zen-cronic

🏠 (Internal)

• refactor(context-zone-peer-dep): use explicit exports #4785 @pichlermarc
• refactor(context-async-hooks): use explicit exports #4785 @pichlermarc

0.52.1

🚀 (Enhancement)

• refactor(instrumentation-fetch): move fetch to use SEMATRR #4632
• refactor(otlp-transformer): use explicit exports #4785 @pichlermarc

🐛 (Bug Fix)

• fix(sdk-node): register context manager if no tracer options are provided #4781 @pichlermarc
• fix(instrumentation): Update import-in-the-middle to fix numerous bugs #4806 @timfish
• chore(instrumentation): Use a caret version for import-in-the-middle dependency #4810 @timfish

🏠 (Internal)

• test: add npm run maint:regenerate-test-certs maintenance script and regenerate recently expired test certs #4777

1.25.0

🚀 (Enhancement)

• feat: support node 22 #4666 @dyladan
• feat(context-zone*): support zone.js 0.12.x #4376 @maldago
• refactor(core): Use tree-shakeable string constants for semconv #4739 @JohannesHuster
• refactor(shim-opentracing): Use tree-shakeable string constants for semconv #4746 @JohannesHuster
• refactor(sdk-trace-web): Use tree-shakeable string constants for semconv #4747 @JohannesHuster
• refactor(sdk-trace-node): Use tree-shakeable string constants for semconv #4748 @JohannesHuster
• refactor(sdk-trace-base): Use tree-shakeable string constants for semconv #4749 @JohannesHuster
• refactor(resources): update deprecated semconv to use exported strings #4755 @JamieDanielson
• refactor(exporters): update deprecated semconv to use exported strings #4756 @JamieDanielson

📚 (Refine Doc)

• refactor(examples): use new exported string constants for semconv in examples/esm-http-ts #4758 @Zen-cronic
• refactor(examples): use new exported string constants for semconv in examples/basic-tracer-node #4759 @Zen-cronic
• refactor(examples): use new exported string constants for semconv in examples/http #4750 @Zen-cronic
• refactor(examples): use new exported string constants for semconv in examples/grpc-js #4760 @Zen-cronic
• refactor(examples): use new exported string constants for semconv in examples/otlp-exporter-node #4762 @Zen-cronic
• refactor(examples): use new exported string constants for semconv in examples/opentracing-shim #4761 @Zen-cronic

0.52.0

💥 Breaking Change

• feat(exporter--otlp-)!: move serialization for Node.js exporters to @opentelemetry/otlp-transformer #4542 @pichlermarc
  • Breaking changes:
    • (user-facing) convert() now returns an empty object and will be removed in a follow-up
    • (internal) OTLPExporterNodeBase now has additional constructor parameters that are required
    • (internal) OTLPExporterNodeBase now has an additional ResponseType type parameter
• feat(exporter--otlp-)!: move serialization for Node.js exporters to @opentelemetry/otlp-transformer #4581 @pichlermarc
  • Breaking changes:
    • (user-facing) convert() has been removed from all exporters
    • (internal) OTLPExporterBrowserBase: RequestType has been replaced by a ResponseType type-argument
    • (internal) OTLPExporterNodeBase: ServiceRequest has been replaced by a ServiceResponse type-argument
    • (internal) the @opentelemetry/otlp-exporter-proto-base package has been removed, and will from now on be deprecated in npm
• feat(instrumentation): remove default value for config in base instrumentation constructor #4695: @blumamir
• fix(instrumentation)!: remove unused supportedVersions from Instrumentation interface #4694 @blumamir
• feat(instrumentation)!: simplify registerInstrumentations() API
  • Breaking changes:
    • removes InstrumentationOptions type
    • occurrences of InstrumentationOptions are now replaced by (Instrumentation | Instrumentation[])[]
      • migrate usages of registerInstrumentations({instrumentations: fooInstrumentation}) to registerInstrumentations({instrumentations: [fooInstrumentation]})
      • passing Instrumentation classes to registerInstrumentations() is now not possible anymore.
• feat(sdk-node)!: simplify type of instrumentations option
  • Breaking changes:
    • replaces InstrumentationOptions with (Instrumentation | Instrumentation[])[]

🚀 (Enhancement)

• feat(instrumentation): apply unwrap before wrap in base class #4692
• feat(instrumentation): add util to execute span customization hook in base class #4663 @blumamir
• feat(instrumentation): generic config type in instrumentation base #4659 @blumamir
• feat: support node 22 #4666 @dyladan
• feat(propagator-aws-xray-lambda): add AWS Xray Lambda propagator 4554
• refactor(instrumentation-xml-http-request): use exported strings for semantic attributes. #4681

🐛 (Bug Fix)

• fix(instrumentation): Update import-in-the-middle to fix numerous bugs #4745 @timfish

📚 (Refine Doc)

• docs(instrumentation): better docs for supportedVersions option #4693 @blumamir
• docs: align all supported versions to a common format #4696 @blumamir
• refactor(examples): use new exported string constants for semconv in experimental/examples/opencensus-shim #4763 @Zen-cronic

1.9.0

🚀 (Enhancement)

• feat(metrics): added synchronous gauge #4528 @clintonb
• feat(api): allow adding span links after span creation #4536 @seemk
  • This change is non-breaking for end-users, but breaking for Trace SDK implmentations in accordance with the specification as new features need to be implemented.
• feat: support node 22 #4666 @dyladan

1.24.1

🐛 (Bug Fix)

• fix(core): align inconsistent behavior of getEnv() and getEnvWithoutDefaults() when a process polyfill is used #4648 @pichlermarc
  • getEnvWithoutDefaults() would use process.env if it was defined when running in a browser, while getEnv() would always use _globalThis. Now both use _globalThis when running in a browser.
• fix(resources): prevent circular import (resource -> detector -> resource -> ...) #4653 @pichlermarc
  • fixes a circular import warning which would appear in rollup when bundling @opentelemetry/resources
• fix(exporter-metrics-otlp-grpc): add explicit otlp-exporter-base dependency to exporter-metrics-otlp-grpc #4678 @AkselAllas