build(deps): bump the nodejs-other group across 2 directories with 51 updates

[dependabot]

Bumps the nodejs-other group with 51 updates in the /nodejs directory:

Package	From	To
typescript	5.7.3	5.8.3
@opentelemetry/api-logs	0.57.2	0.200.0
@opentelemetry/context-async-hooks	1.30.1	2.0.0
@opentelemetry/core	1.30.1	2.0.0
@opentelemetry/exporter-logs-otlp-http	0.57.2	0.200.0
@opentelemetry/exporter-metrics-otlp-http	0.57.2	0.200.0
@opentelemetry/exporter-trace-otlp-http	0.57.2	0.200.0
@opentelemetry/instrumentation	0.57.2	0.200.0
@opentelemetry/instrumentation-amqplib	0.46.1	0.47.0
@opentelemetry/instrumentation-aws-lambda	0.50.3	0.51.0
@opentelemetry/instrumentation-aws-sdk	0.49.1	0.51.0
@opentelemetry/instrumentation-bunyan	0.45.1	0.46.0
@opentelemetry/instrumentation-cassandra-driver	0.45.1	0.46.0
@opentelemetry/instrumentation-connect	0.43.1	0.44.0
@opentelemetry/instrumentation-dataloader	0.16.1	0.17.0
@opentelemetry/instrumentation-dns	0.43.1	0.44.0
@opentelemetry/instrumentation-express	0.47.1	0.48.0
@opentelemetry/instrumentation-fs	0.19.1	0.20.0
@opentelemetry/instrumentation-graphql	0.47.1	0.48.0
@opentelemetry/instrumentation-grpc	0.57.2	0.200.0
@opentelemetry/instrumentation-hapi	0.45.2	0.46.0
@opentelemetry/instrumentation-http	0.57.2	0.200.0
@opentelemetry/instrumentation-ioredis	0.47.1	0.48.0
@opentelemetry/instrumentation-kafkajs	0.7.1	0.9.0
@opentelemetry/instrumentation-knex	0.44.1	0.45.0
@opentelemetry/instrumentation-koa	0.47.1	0.48.0
@opentelemetry/instrumentation-memcached	0.43.1	0.44.0
@opentelemetry/instrumentation-mongodb	0.52.0	0.53.0
@opentelemetry/instrumentation-mongoose	0.46.1	0.47.0
@opentelemetry/instrumentation-mysql	0.45.1	0.46.0
@opentelemetry/instrumentation-mysql2	0.45.2	0.46.0
@opentelemetry/instrumentation-nestjs-core	0.44.1	0.46.0
@opentelemetry/instrumentation-net	0.43.1	0.44.0
@opentelemetry/instrumentation-pg	0.51.1	0.52.0
@opentelemetry/instrumentation-pino	0.46.1	0.47.0
@opentelemetry/instrumentation-redis	0.46.1	0.47.0
@opentelemetry/instrumentation-restify	0.45.1	0.46.0
@opentelemetry/instrumentation-socket.io	0.46.1	0.47.0
@opentelemetry/instrumentation-undici	0.10.1	0.11.0
@opentelemetry/instrumentation-winston	0.44.1	0.45.0
@opentelemetry/propagator-aws-xray	1.26.2	2.0.0
@opentelemetry/propagator-aws-xray-lambda	0.53.2	0.54.0
@opentelemetry/resource-detector-aws	1.12.0	2.0.0
@opentelemetry/resources	1.30.1	2.0.0
@opentelemetry/sdk-logs	0.57.2	0.200.0
@opentelemetry/sdk-metrics	1.30.1	2.0.0
@opentelemetry/sdk-trace-base	1.30.1	2.0.0
sinon	19.0.2	20.0.0
webpack	5.98.0	5.99.5
@types/aws-lambda	8.10.147	8.10.149
@types/node	22.13.5	22.14.0

Bumps the nodejs-other group with 3 updates in the /nodejs/sample-apps/aws-sdk directory: typescript, @types/aws-lambda and @types/node.

Updates typescript from 5.7.3 to 5.8.3

Release notes

Sourced from typescript's releases.

TypeScript 5.8.3

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).
• fixed issues query for Typescript 5.8.2 (Stable).
• fixed issues query for Typescript 5.8.3 (Stable).

Downloads are available on:

• npm

TypeScript 5.8

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).
• fixed issues query for Typescript 5.8.2 (Stable).

Downloads are available on:

• npm

TypeScript 5.8 RC

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).

Downloads are available on:

• npm

TypeScript 5.8 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).

Downloads are available on:

• npm

Commits

• 83dc0bb Convert release publishing inputs into parameters (#61523)
• ba663f6 Exclude completions of binding pattern variable initializers (#52723)
• 7205eda Bump github/codeql-action from 3.28.12 to 3.28.13 in the github-actions group...
• 89c572c Fixed a symbol display crash on expando members write locations (#55478)
• 7b26d2e Fix incorrect name in new release pipeline (#61514)
• c7a559e Add new release publisher yaml (#61491)
• 29e6d66 Fix lib.includes('dom') check in containerSeemsToBeEmptyDomElement (#61481)
• 19b7772 Bump the github-actions group with 4 updates (#61474)
• 4dc677b Fix errors on type assertions in erasableSyntaxOnly (#61452)
• ee3dd72 fix(60908): Unexpected "'Type' is declared but its value is never read." erro...
• Additional commits viewable in compare view

Updates @opentelemetry/api-logs from 0.57.2 to 0.200.0

Release notes

Sourced from @​opentelemetry/api-logs's releases.

experimental/v0.200.0

0.200.0

Summary

• The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
• The minimum supported TypeScript version has been raised to 5.0.4.
• The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
• The public interface has changed
  • for notes on migrating to 2.x / 0.200.x see the upgrade guide
• Only stable versions 2.0.0 are compatible with this release

💥 Breaking Change

• feat(exporter-prometheus)!: stop the using type field to enforce naming conventions #5291 @​chancancode
  • Any non-monotonic sums will now be treated as counters and will therefore include the _total suffix.
• feat(shim-opencenus)!: stop mapping removed Instrument type to OpenTelemetry metrics #5291 @​chancancode
  • The internal OpenTelemetry data model dropped the concept of instrument type on exported metrics, therefore mapping it is not necessary anymore.
• feat(instrumentation-fetch)!: passthrough original response to applyCustomAttributes hook #5281 @​chancancode
  • Previously, the fetch instrumentation code unconditionally clones every fetch() response in order to preserve the ability for the applyCustomAttributes hook to consume the response body. This is fundamentally unsound, as it forces the browser to buffer and retain the response body until it is fully received and read, which crates unnecessary memory pressure on large or long-running response streams. In extreme cases, this is effectively a memory leak and can cause the browser tab to crash. If your use case for applyCustomAttributes requires access to the response body, please chime in on #5293.
• chore!: Raise the minimum supported Node.js version to ^18.19.0 || >=20.6.0. Support for Node.js 14, 16, and early minor versions of 18 and 20 have been dropped. This applies to all packages except the 'api' and 'semantic-conventions' packages. #5395 @​trentm
• feat(sdk-node)!: use IMetricReader over MetricReader #5311
  • (user-facing): NodeSDKConfiguration now provides the more general IMetricReader type over MetricReader
• feat(exporter-metrics-otlp-http)!: do not read environment variables from window in browsers #5473 @​pichlermarc
  • (user-facing): all configuration previously possible via window.OTEL_* is now not supported anymore, please pass configuration options to constructors instead.
  • Note: Node.js environment variable configuration continues to work as-is.
• feat(sdk-logs)!: do not read environment variables from window in browsers #5472 @​pichlermarc
  • (user-facing): all configuration previously possible via window.OTEL_* is now not supported anymore, please pass configuration options to constructors instead.
    • Note: Node.js environment variable configuration continues to work as-is.

🚀 (Enhancement)

• feat(instrumentation-fetch): add a requestHook option #5380
• feat(instrumentation): re-export initialize function from import-in-the-middle #5123
• feat(sdk-node): lower diagnostic level #5360 @​cjihrig
• feat(exporter-prometheus): add additional attributes option #5317 @​marius-a-mueller
  • Add withResourceConstantLabels option to ExporterConfig. It can be used to define a regex pattern to choose which resource attributes will be used as static labels on the metrics. The default is to not set any static labels.

🐛 (Bug Fix)

• fix(instrumentation-grpc): monitor error events with events.errorMonitor #5369 @​cjihrig
• fix(exporter-metrics-otlp-http): browser OTLPMetricExporter was not passing config to OTLPMetricExporterBase super class #5331 @​trentm
• fix(instrumentation-fetch, instrumentation-xhr): Ignore network events with zero-timings #5332 @​chancancode
• fix(exporter-logs/trace-otlp-grpc): fix error for missing dependency otlp-exporter-base #5412 @​JamieDanielson

🏠 (Internal)

• chore(instrumentation-grpc): remove unused findIndex() function #5372 @​cjihrig
• refactor(otlp-exporter-base): remove unnecessary isNaN() checks #5374 @​cjihrig
• refactor(exporter-prometheus): remove unnecessary isNaN() check #5377 @​cjihrig

... (truncated)

Changelog

Sourced from @​opentelemetry/api-logs's changelog.

CHANGELOG

All notable changes to this project will be documented in this file.

For API changes, see the API CHANGELOG. For experimental package changes, see the experimental CHANGELOG. For semantic convention package changes, see the semconv CHANGELOG. For notes on migrating to 2.x / 0.200.x see the upgrade guide.

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

• fix(resources): guard asynchronous resource attribute rejections from causing unhandled promise rejection #5544 @​dyladan
• fix(resource): do not trigger Accessing resource attributes before async attributes settled warning when detecting resources #5546 @​dyladan
  • verbose logging of detected resource removed

📚 Documentation

🏠 Internal

2.0.0

Summary

• The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
• The minimum supported TypeScript version has been raised to 5.0.4.
• The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
• The public interface has changed
  • for notes on migrating to 2.x / 0.200.x see the upgrade guide
• Only experimental versions 0.200.0 are compatible with this release

💥 Breaking Change

• feat(sdk-trace-base)!: Add parentSpanContext and remove parentSpanId from Span and ReadableSpan #5450 @​JacksonWeber
  • (user-facing): the SDK's Spans parentSpanId was replaced by parentSpanContext, to migrate to the new property, please replace span.parentSpanId -> span.parentSpanContext?.spanId
• feat(sdk-metrics)!: drop deprecated type field on MetricDescriptor #5291 @​chancancode
• feat(sdk-metrics)!: drop deprecated InstrumentDescriptor type; use MetricDescriptor instead #5277 @​chancancode
• feat(sdk-metrics)!: bump minimum version of @opentelemetry/api peer dependency to 1.9.0 #5254 @​chancancode
• chore(shim-opentracing): replace deprecated SpanAttributes #4430 @​JamieDanielson
• chore(otel-core): replace deprecated SpanAttributes #4408 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• chore(otel-resources): replace deprecated SpanAttributes #4428 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• feat(sdk-metrics)!: replace attributeKeys with custom processors option #4532 @​pichlermarc

... (truncated)

Commits

• 7fde940 chore: prepare release 2.0.0/0.200.0 (#5521)
• ecd67de doc: add section to SDK 2.x migration guide for implementors of resource dete...
• eaebf76 chore: prepare release 2.0.0-rc.1/0.200.0-rc.1 (#5534)
• e947bd9 chore(deps): update dependency babel-loader to v10 (#5518)
• 5e20647 fix(deps): update dependency axios to v1.8.2 [security] (#5532)
• 78fc472 chore(deps): lock file maintenance (#5531)
• 693b09d fix(core): avoid using util in configuration.ts for browser compatibility (#5...
• 92fde6a chore: prepare 2.0.0-dev.1/0.200.0-dev.1 pre-release (#5512)
• 04b3210 doc: upgrade/migration guide for SDK 2.0 (#5513)
• cb48266 fix(deps): update dependency import-in-the-middle to v1.13.1 (#5517)
• Additional commits viewable in compare view

Updates @opentelemetry/context-async-hooks from 1.30.1 to 2.0.0

Release notes

Sourced from @​opentelemetry/context-async-hooks's releases.

v2.0.0

2.0.0

Summary

• The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
• The minimum supported TypeScript version has been raised to 5.0.4.
• The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
• The public interface has changed
  • for notes on migrating to 2.x / 0.200.x see the upgrade guide
• Only experimental versions 0.200.0 are compatible with this release

💥 Breaking Change

• feat(sdk-trace-base)!: Add parentSpanContext and remove parentSpanId from Span and ReadableSpan #5450 @​JacksonWeber
  • (user-facing): the SDK's Spans parentSpanId was replaced by parentSpanContext, to migrate to the new property, please replace span.parentSpanId -> span.parentSpanContext?.spanId
• feat(sdk-metrics)!: drop deprecated type field on MetricDescriptor #5291 @​chancancode
• feat(sdk-metrics)!: drop deprecated InstrumentDescriptor type; use MetricDescriptor instead #5277 @​chancancode
• feat(sdk-metrics)!: bump minimum version of @opentelemetry/api peer dependency to 1.9.0 #5254 @​chancancode
• chore(shim-opentracing): replace deprecated SpanAttributes #4430 @​JamieDanielson
• chore(otel-core): replace deprecated SpanAttributes #4408 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• chore(otel-resources): replace deprecated SpanAttributes #4428 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• feat(sdk-metrics)!: replace attributeKeys with custom processors option #4532 @​pichlermarc
• refactor(sdk-trace-base)!: replace SpanAttributes with Attributes #5009 @​david-luna
• refactor(resources)!: replace ResourceAttributes with Attributes #5016 @​david-luna
• feat(sdk-metrics)!: drop View and Aggregation in favor of ViewOptions and AggregationOption #4931 @​pichlermarc
• refactor(sdk-trace-base)!: remove new Span constructor in favor of Tracer.startSpan API #5048 @​david-luna
• refactor(sdk-trace-base)!: remove BasicTracerProvider.addSpanProcessor API in favor of constructor options. #5134 @​david-luna
• refactor(sdk-trace-base)!: make resource property private in BasicTracerProvider and remove getActiveSpanProcessor API. #5192 @​david-luna
• feat(sdk-metrics)!: extract IMetricReader interface and use it over abstract class #5311
  • (user-facing): MeterProviderOptions now provides the more general IMetricReader type over MetricReader
  • If you accept MetricReader in your public interface, consider accepting the more general IMetricReader instead to avoid unintentional breaking changes
• feat(sdk-trace)!: remove ability to have BasicTracerProvider instantiate exporters #5239 @​pichlermarc
  • When extending BasicTracerProvider, the class offered multiple methods to facilitate the creation of exporters and auto-pairing with SpanProcessors.
    • This functionality has been removed - users may now pass SpanProcessors to the base class constructor when extending
    • (user-facing): _registeredExporters has been removed
    • (user-facing): _getSpanExporter has been removed
    • (user-facing): _buildExporterFromEnv has been removed
• feat(core)!: remove deprecated IdGenerator and RandomIdGenerator #5309 @​pichlermarc
• feat(core)!: remove deprecated type InstrumentationLibrary #5308 @​pichlermarc
  • (user-facing): please use equivalent type InstrumentationScope instead
• feat(sdk-trace-base)!: replace usages fo InstrumentationLibrary with InstrumentationScope #5308 @​pichlermarc
  • (user-facing) rename Tracer.instrumentationLibrary -> Tracer.instrumentationScope
  • (user-facing) rename ReadableSpan.instrumentationLibrary -> ReadableSpan.instrumentationScope
    • also renames the property in implementations of ReadableSpan
• feat(exporter-jaeger): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
• feat(exporter-zipkin): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
• chore!: update typescript to version 5.0.4 #5145 @​david-luna

... (truncated)

Changelog

Sourced from @​opentelemetry/context-async-hooks's changelog.

2.0.0

Summary

• The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
• The minimum supported TypeScript version has been raised to 5.0.4.
• The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
• The public interface has changed
  • for notes on migrating to 2.x / 0.200.x see the upgrade guide
• Only experimental versions 0.200.0 are compatible with this release

💥 Breaking Change

• feat(sdk-trace-base)!: Add parentSpanContext and remove parentSpanId from Span and ReadableSpan #5450 @​JacksonWeber
  • (user-facing): the SDK's Spans parentSpanId was replaced by parentSpanContext, to migrate to the new property, please replace span.parentSpanId -> span.parentSpanContext?.spanId
• feat(sdk-metrics)!: drop deprecated type field on MetricDescriptor #5291 @​chancancode
• feat(sdk-metrics)!: drop deprecated InstrumentDescriptor type; use MetricDescriptor instead #5277 @​chancancode
• feat(sdk-metrics)!: bump minimum version of @opentelemetry/api peer dependency to 1.9.0 #5254 @​chancancode
• chore(shim-opentracing): replace deprecated SpanAttributes #4430 @​JamieDanielson
• chore(otel-core): replace deprecated SpanAttributes #4408 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• chore(otel-resources): replace deprecated SpanAttributes #4428 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• feat(sdk-metrics)!: replace attributeKeys with custom processors option #4532 @​pichlermarc
• refactor(sdk-trace-base)!: replace SpanAttributes with Attributes #5009 @​david-luna
• refactor(resources)!: replace ResourceAttributes with Attributes #5016 @​david-luna
• feat(sdk-metrics)!: drop View and Aggregation in favor of ViewOptions and AggregationOption #4931 @​pichlermarc
• refactor(sdk-trace-base)!: remove new Span constructor in favor of Tracer.startSpan API #5048 @​david-luna
• refactor(sdk-trace-base)!: remove BasicTracerProvider.addSpanProcessor API in favor of constructor options. #5134 @​david-luna
• refactor(sdk-trace-base)!: make resource property private in BasicTracerProvider and remove getActiveSpanProcessor API. #5192 @​david-luna
• feat(sdk-metrics)!: extract IMetricReader interface and use it over abstract class #5311
  • (user-facing): MeterProviderOptions now provides the more general IMetricReader type over MetricReader
  • If you accept MetricReader in your public interface, consider accepting the more general IMetricReader instead to avoid unintentional breaking changes
• feat(sdk-trace)!: remove ability to have BasicTracerProvider instantiate exporters #5239 @​pichlermarc
  • When extending BasicTracerProvider, the class offered multiple methods to facilitate the creation of exporters and auto-pairing with SpanProcessors.
    • This functionality has been removed - users may now pass SpanProcessors to the base class constructor when extending
    • (user-facing): _registeredExporters has been removed
    • (user-facing): _getSpanExporter has been removed
    • (user-facing): _buildExporterFromEnv has been removed
• feat(core)!: remove deprecated IdGenerator and RandomIdGenerator #5309 @​pichlermarc
• feat(core)!: remove deprecated type InstrumentationLibrary #5308 @​pichlermarc
  • (user-facing): please use equivalent type InstrumentationScope instead
• feat(sdk-trace-base)!: replace usages fo InstrumentationLibrary with InstrumentationScope #5308 @​pichlermarc
  • (user-facing) rename Tracer.instrumentationLibrary -> Tracer.instrumentationScope
  • (user-facing) rename ReadableSpan.instrumentationLibrary -> ReadableSpan.instrumentationScope
    • also renames the property in implementations of ReadableSpan
• feat(exporter-jaeger): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
• feat(exporter-zipkin): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
• chore!: update typescript to version 5.0.4 #5145 @​david-luna
  • (user-facing) dropped support for typescript@<5.0.4

... (truncated)

Commits

• 7fde940 chore: prepare release 2.0.0/0.200.0 (#5521)
• ecd67de doc: add section to SDK 2.x migration guide for implementors of resource dete...
• eaebf76 chore: prepare release 2.0.0-rc.1/0.200.0-rc.1 (#5534)
• e947bd9 chore(deps): update dependency babel-loader to v10 (#5518)
• 5e20647 fix(deps): update dependency axios to v1.8.2 [security] (#5532)
• 78fc472 chore(deps): lock file maintenance (#5531)
• 693b09d fix(core): avoid using util in configuration.ts for browser compatibility (#5...
• 92fde6a chore: prepare 2.0.0-dev.1/0.200.0-dev.1 pre-release (#5512)
• 04b3210 doc: upgrade/migration guide for SDK 2.0 (#5513)
• cb48266 fix(deps): update dependency import-in-the-middle to v1.13.1 (#5517)
• Additional commits viewable in compare view

Updates @opentelemetry/core from 1.30.1 to 2.0.0

Release notes

Sourced from @​opentelemetry/core's releases.

v2.0.0

2.0.0

Summary

• The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
• The minimum supported TypeScript version has been raised to 5.0.4.
• The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
• The public interface has changed
  • for notes on migrating to 2.x / 0.200.x see the upgrade guide
• Only experimental versions 0.200.0 are compatible with this release

💥 Breaking Change

• feat(sdk-trace-base)!: Add parentSpanContext and remove parentSpanId from Span and ReadableSpan #5450 @​JacksonWeber
  • (user-facing): the SDK's Spans parentSpanId was replaced by parentSpanContext, to migrate to the new property, please replace span.parentSpanId -> span.parentSpanContext?.spanId
• feat(sdk-metrics)!: drop deprecated type field on MetricDescriptor #5291 @​chancancode
• feat(sdk-metrics)!: drop deprecated InstrumentDescriptor type; use MetricDescriptor instead #5277 @​chancancode
• feat(sdk-metrics)!: bump minimum version of @opentelemetry/api peer dependency to 1.9.0 #5254 @​chancancode
• chore(shim-opentracing): replace deprecated SpanAttributes #4430 @​JamieDanielson
• chore(otel-core): replace deprecated SpanAttributes #4408 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• chore(otel-resources): replace deprecated SpanAttributes #4428 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• feat(sdk-metrics)!: replace attributeKeys with custom processors option #4532 @​pichlermarc
• refactor(sdk-trace-base)!: replace SpanAttributes with Attributes #5009 @​david-luna
• refactor(resources)!: replace ResourceAttributes with Attributes #5016 @​david-luna
• feat(sdk-metrics)!: drop View and Aggregation in favor of ViewOptions and AggregationOption #4931 @​pichlermarc
• refactor(sdk-trace-base)!: remove new Span constructor in favor of Tracer.startSpan API #5048 @​david-luna
• refactor(sdk-trace-base)!: remove BasicTracerProvider.addSpanProcessor API in favor of constructor options. #5134 @​david-luna
• refactor(sdk-trace-base)!: make resource property private in BasicTracerProvider and remove getActiveSpanProcessor API. #5192 @​david-luna
• feat(sdk-metrics)!: extract IMetricReader interface and use it over abstract class #5311
  • (user-facing): MeterProviderOptions now provides the more general IMetricReader type over MetricReader
  • If you accept MetricReader in your public interface, consider accepting the more general IMetricReader instead to avoid unintentional breaking changes
• feat(sdk-trace)!: remove ability to have BasicTracerProvider instantiate exporters #5239 @​pichlermarc
  • When extending BasicTracerProvider, the class offered multiple methods to facilitate the creation of exporters and auto-pairing with SpanProcessors.
    • This functionality has been removed - users may now pass SpanProcessors to the base class constructor when extending
    • (user-facing): _registeredExporters has been removed
    • (user-facing): _getSpanExporter has been removed
    • (user-facing): _buildExporterFromEnv has been removed
• feat(core)!: remove deprecated IdGenerator and RandomIdGenerator #5309 @​pichlermarc
• feat(core)!: remove deprecated type InstrumentationLibrary #5308 @​pichlermarc
  • (user-facing): please use equivalent type InstrumentationScope instead
• feat(sdk-trace-base)!: replace usages fo InstrumentationLibrary with InstrumentationScope #5308 @​pichlermarc
  • (user-facing) rename Tracer.instrumentationLibrary -> Tracer.instrumentationScope
  • (user-facing) rename ReadableSpan.instrumentationLibrary -> ReadableSpan.instrumentationScope
    • also renames the property in implementations of ReadableSpan
• feat(exporter-jaeger): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
• feat(exporter-zipkin): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
• chore!: update typescript to version 5.0.4 #5145 @​david-luna

... (truncated)

Changelog

Sourced from @​opentelemetry/core's changelog.

2.0.0

Summary

• The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
• The minimum supported TypeScript version has been raised to 5.0.4.
• The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
• The public interface has changed
  • for notes on migrating to 2.x / 0.200.x see the upgrade guide
• Only experimental versions 0.200.0 are compatible with this release

💥 Breaking Change

• feat(sdk-trace-base)!: Add parentSpanContext and remove parentSpanId from Span and ReadableSpan #5450 @​JacksonWeber
  • (user-facing): the SDK's Spans parentSpanId was replaced by parentSpanContext, to migrate to the new property, please replace span.parentSpanId -> span.parentSpanContext?.spanId
• feat(sdk-metrics)!: drop deprecated type field on MetricDescriptor #5291 @​chancancode
• feat(sdk-metrics)!: drop deprecated InstrumentDescriptor type; use MetricDescriptor instead #5277 @​chancancode
• feat(sdk-metrics)!: bump minimum version of @opentelemetry/api peer dependency to 1.9.0 #5254 @​chancancode
• chore(shim-opentracing): replace deprecated SpanAttributes #4430 @​JamieDanielson
• chore(otel-core): replace deprecated SpanAttributes #4408 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• chore(otel-resources): replace deprecated SpanAttributes #4428 @​JamieDanielson
• feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
• feat(sdk-metrics)!: replace attributeKeys with custom processors option #4532 @​pichlermarc
• refactor(sdk-trace-base)!: replace SpanAttributes with Attributes #5009 @​david-luna
• refactor(resources)!: replace ResourceAttributes with Attributes #5016 @​david-luna
• feat(sdk-metrics)!: drop View and Aggregation in favor of ViewOptions and AggregationOption #4931 @​pichlermarc
• refactor(sdk-trace-base)!: remove new Span constructor in favor of Tracer.startSpan API #5048 @​david-luna
• refactor(sdk-trace-base)!: remove BasicTracerProvider.addSpanProcessor API in favor of constructor options. #5134 @​david-luna
• refactor(sdk-trace-base)!: make resource property private in BasicTracerProvider and remove getActiveSpanProcessor API. #5192 @​david-luna
• feat(sdk-metrics)!: extract IMetricReader interface and use it over abstract class

[wpessers]

@serkan-ozal see my comment above. I can work on these upgrades but will take some more time than simple dependency upgrades

[serkan-ozal]

@wpessers There are some breaking changes in the OTEL JS SDK v2.0 (0.200.0), so updating dependencies to that version requires special attention and testing.

So I think, we can release without upgrade to OTEL JS SDK v2.0 and then handle this update.
WDYT @tylerbenson?

[tylerbenson]

I don't have a strong preference either way.

[serkan-ozal]

@dependabot rebase