chore(deps): bump the opentelemetry group across 1 directory with 56 updates

[dependabot]

Bumps the opentelemetry group with 55 updates in the /packages/opentelemetry-node directory:

Package	From	To
@opentelemetry/core	2.0.0	2.0.1
@opentelemetry/exporter-logs-otlp-grpc	0.200.0	0.201.0
@opentelemetry/exporter-logs-otlp-http	0.200.0	0.201.0
@opentelemetry/exporter-logs-otlp-proto	0.200.0	0.201.0
@opentelemetry/exporter-metrics-otlp-grpc	0.200.0	0.201.0
@opentelemetry/exporter-metrics-otlp-http	0.200.0	0.201.0
@opentelemetry/exporter-metrics-otlp-proto	0.200.0	0.201.0
@opentelemetry/instrumentation-amqplib	0.47.0	0.48.0
@opentelemetry/instrumentation-aws-sdk	0.50.0	0.53.0
@opentelemetry/instrumentation-bunyan	0.46.0	0.47.0
@opentelemetry/instrumentation-cassandra-driver	0.46.0	0.47.0
@opentelemetry/instrumentation-connect	0.44.0	0.45.0
@opentelemetry/instrumentation-cucumber	0.15.0	0.16.0
@opentelemetry/instrumentation-dataloader	0.17.0	0.18.0
@opentelemetry/instrumentation-dns	0.44.0	0.45.0
@opentelemetry/instrumentation-express	0.48.1	0.50.0
@opentelemetry/instrumentation-fastify	0.45.0	0.46.0
@opentelemetry/instrumentation-fs	0.20.0	0.21.0
@opentelemetry/instrumentation-generic-pool	0.44.0	0.45.0
@opentelemetry/instrumentation-graphql	0.48.0	0.49.0
@opentelemetry/instrumentation-grpc	0.200.0	0.201.0
@opentelemetry/instrumentation-hapi	0.46.0	0.47.0
@opentelemetry/instrumentation-http	0.200.0	0.201.0
@opentelemetry/instrumentation-ioredis	0.48.0	0.49.0
@opentelemetry/instrumentation-kafkajs	0.8.0	0.10.0
@opentelemetry/instrumentation-knex	0.45.0	0.46.0
@opentelemetry/instrumentation-koa	0.48.0	0.49.0
@opentelemetry/instrumentation-lru-memoizer	0.45.0	0.46.0
@opentelemetry/instrumentation-memcached	0.44.0	0.45.0
@opentelemetry/instrumentation-mongodb	0.53.0	0.54.0
@opentelemetry/instrumentation-mongoose	0.47.0	0.48.0
@opentelemetry/instrumentation-mysql	0.46.0	0.47.0
@opentelemetry/instrumentation-mysql2	0.46.0	0.47.0
@opentelemetry/instrumentation-nestjs-core	0.45.0	0.47.0
@opentelemetry/instrumentation-net	0.44.0	0.45.0
@opentelemetry/instrumentation-pg	0.52.0	0.53.0
@opentelemetry/instrumentation-pino	0.47.0	0.48.0
@opentelemetry/instrumentation-redis	0.47.0	0.48.0
@opentelemetry/instrumentation-redis-4	0.47.0	0.48.0
@opentelemetry/instrumentation-restify	0.46.0	0.47.0
@opentelemetry/instrumentation-router	0.45.0	0.46.0
@opentelemetry/instrumentation-runtime-node	0.13.0	0.15.0
@opentelemetry/instrumentation-socket.io	0.47.0	0.48.0
@opentelemetry/instrumentation-tedious	0.19.0	0.20.0
@opentelemetry/instrumentation-undici	0.11.0	0.12.0
@opentelemetry/instrumentation-winston	0.45.0	0.46.0
@opentelemetry/resource-detector-alibaba-cloud	0.31.0	0.31.1
@opentelemetry/resource-detector-aws	2.0.0	2.1.0
@opentelemetry/resource-detector-azure	0.7.0	0.8.0
@opentelemetry/resource-detector-container	0.7.0	0.7.1
@opentelemetry/resources	2.0.0	2.0.1
@opentelemetry/sdk-logs	0.200.0	0.201.0
@opentelemetry/sdk-metrics	2.0.0	2.0.1
@opentelemetry/sdk-node	0.200.0	0.201.0
@opentelemetry/winston-transport	0.11.0	0.12.0

Updates @opentelemetry/core from 2.0.0 to 2.0.1

Release notes

Sourced from @​opentelemetry/core's releases.

v2.0.1

2.0.1

🐛 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
• fix(resource): use dynamic import over require to improve ESM compliance #5298 @​xiaoxiangmoe

📚 Documentation

• refactor(metrics): Updated metrics samples to no longer treat sdk.start() as async #5617 @​JacksonWeber

🏠 Internal

• refactor(sdk-trace-base): update semconv usage to ATTR_ exports #5669 @​trentm
• refactor(sdk-trace-web): update semconv usage to ATTR_ exports #5672 @​trentm
• refactor(resources): update semconv usage to ATTR_ exports #5666 @​trentm
• test(sdk-metrics): fix multiple problematic assertRejects() calls #5611 @​cjihrig
• refactor: replace assertRejects() with assert.rejects() #5614 @​cjihrig
• refactor(core): migrate from deprecated semconv constants #5575 @​alumni55748
• refactor(opentelemetry-core): simplify parseKeyPairsIntoRecord() #5610 @​cjihrig

Changelog

Sourced from @​opentelemetry/core's changelog.

2.0.1

🐛 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
• fix(resource): use dynamic import over require to improve ESM compliance #5298 @​xiaoxiangmoe

📚 Documentation

• refactor(metrics): Updated metrics samples to no longer treat sdk.start() as async #5617 @​JacksonWeber

🏠 Internal

• refactor(sdk-trace-base): update semconv usage to ATTR_ exports #5669 @​trentm
• refactor(sdk-trace-web): update semconv usage to ATTR_ exports #5672 @​trentm
• refactor(resources): update semconv usage to ATTR_ exports #5666 @​trentm
• test(sdk-metrics): fix multiple problematic assertRejects() calls #5611 @​cjihrig
• refactor: replace assertRejects() with assert.rejects() #5614 @​cjihrig
• refactor(core): migrate from deprecated semconv constants #5575 @​alumni55748
• refactor(opentelemetry-core): simplify parseKeyPairsIntoRecord() #5610 @​cjihrig

Commits

• 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
• 6803723 fix(deps): update all patch versions (#5685)
• d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
• 56610a0 test: test Node.js 24 in CI (#5661)
• 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
• 373edd9 Revert "fix(sdk-metrics): improve PeriodicExportingMetricReader() constructor...
• 0c21db4 feat(instrumentation-xml-http-request): support migration to stable HTTP semc...
• 0665c85 refactor(sdk-node): update semconv usage to ATTR_ exports (#5668)
• d07d630 refactor(sdk-trace-base): update semconv usage to ATTR_ exports (#5669)
• bc8c94e refactor(sdk-trace-node): update semconv usage to ATTR_ exports (#5670)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-logs-otlp-grpc from 0.200.0 to 0.201.0

Release notes

Sourced from @​opentelemetry/exporter-logs-otlp-grpc's releases.

experimental/v0.201.0

0.201.0

🚀 Features

• feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • See the utility comment.
• feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
• feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

• fix(otlp-transformer): do not throw when deserializing empty JSON response #5551 @​pichlermarc
• fix(instrumentation-http): report stable client metrics response code #9586 @​jtescher
• fix(sdk-node): instantiate baggage processor when env var is set #5634 @​pichlermarc

🏠 Internal

• refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
• refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
  • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
• refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
• test: test Node.js 24 in CI #5661 @​cjihrig

Commits

• 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
• 6803723 fix(deps): update all patch versions (#5685)
• d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
• 56610a0 test: test Node.js 24 in CI (#5661)
• 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
• 373edd9 Revert "fix(sdk-metrics): improve PeriodicExportingMetricReader() constructor...
• 0c21db4 feat(instrumentation-xml-http-request): support migration to stable HTTP semc...
• 0665c85 refactor(sdk-node): update semconv usage to ATTR_ exports (#5668)
• d07d630 refactor(sdk-trace-base): update semconv usage to ATTR_ exports (#5669)
• bc8c94e refactor(sdk-trace-node): update semconv usage to ATTR_ exports (#5670)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-logs-otlp-http from 0.200.0 to 0.201.0

Release notes

Sourced from @​opentelemetry/exporter-logs-otlp-http's releases.

experimental/v0.201.0

0.201.0

🚀 Features

• feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • See the utility comment.
• feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
• feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

• fix(otlp-transformer): do not throw when deserializing empty JSON response #5551 @​pichlermarc
• fix(instrumentation-http): report stable client metrics response code #9586 @​jtescher
• fix(sdk-node): instantiate baggage processor when env var is set #5634 @​pichlermarc

🏠 Internal

• refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
• refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
  • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
• refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
• test: test Node.js 24 in CI #5661 @​cjihrig

Commits

• 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
• 6803723 fix(deps): update all patch versions (#5685)
• d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
• 56610a0 test: test Node.js 24 in CI (#5661)
• 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
• 373edd9 Revert "fix(sdk-metrics): improve PeriodicExportingMetricReader() constructor...
• 0c21db4 feat(instrumentation-xml-http-request): support migration to stable HTTP semc...
• 0665c85 refactor(sdk-node): update semconv usage to ATTR_ exports (#5668)
• d07d630 refactor(sdk-trace-base): update semconv usage to ATTR_ exports (#5669)
• bc8c94e refactor(sdk-trace-node): update semconv usage to ATTR_ exports (#5670)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-logs-otlp-proto from 0.200.0 to 0.201.0

Release notes

Sourced from @​opentelemetry/exporter-logs-otlp-proto's releases.

experimental/v0.201.0

0.201.0

🚀 Features

• feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • See the utility comment.
• feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
• feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

• fix(otlp-transformer): do not throw when deserializing empty JSON response #5551 @​pichlermarc
• fix(instrumentation-http): report stable client metrics response code #9586 @​jtescher
• fix(sdk-node): instantiate baggage processor when env var is set #5634 @​pichlermarc

🏠 Internal

• refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
• refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
  • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
• refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
• test: test Node.js 24 in CI #5661 @​cjihrig

Commits

• 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
• 6803723 fix(deps): update all patch versions (#5685)
• d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
• 56610a0 test: test Node.js 24 in CI (#5661)
• 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
• 373edd9 Revert "fix(sdk-metrics): improve PeriodicExportingMetricReader() constructor...
• 0c21db4 feat(instrumentation-xml-http-request): support migration to stable HTTP semc...
• 0665c85 refactor(sdk-node): update semconv usage to ATTR_ exports (#5668)
• d07d630 refactor(sdk-trace-base): update semconv usage to ATTR_ exports (#5669)
• bc8c94e refactor(sdk-trace-node): update semconv usage to ATTR_ exports (#5670)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-metrics-otlp-grpc from 0.200.0 to 0.201.0

Release notes

Sourced from @​opentelemetry/exporter-metrics-otlp-grpc's releases.

experimental/v0.201.0

0.201.0

🚀 Features

• feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • See the utility comment.
• feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
• feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

• fix(otlp-transformer): do not throw when deserializing empty JSON response #5551 @​pichlermarc
• fix(instrumentation-http): report stable client metrics response code #9586 @​jtescher
• fix(sdk-node): instantiate baggage processor when env var is set #5634 @​pichlermarc

🏠 Internal

• refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
• refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
  • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
• refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
• test: test Node.js 24 in CI #5661 @​cjihrig

Commits

• 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
• 6803723 fix(deps): update all patch versions (#5685)
• d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
• 56610a0 test: test Node.js 24 in CI (#5661)
• 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
• 373edd9 Revert "fix(sdk-metrics): improve PeriodicExportingMetricReader() constructor...
• 0c21db4 feat(instrumentation-xml-http-request): support migration to stable HTTP semc...
• 0665c85 refactor(sdk-node): update semconv usage to ATTR_ exports (#5668)
• d07d630 refactor(sdk-trace-base): update semconv usage to ATTR_ exports (#5669)
• bc8c94e refactor(sdk-trace-node): update semconv usage to ATTR_ exports (#5670)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-metrics-otlp-http from 0.200.0 to 0.201.0

Release notes

Sourced from @​opentelemetry/exporter-metrics-otlp-http's releases.

experimental/v0.201.0

0.201.0

🚀 Features

• feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • See the utility comment.
• feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
• feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

• fix(otlp-transformer): do not throw when deserializing empty JSON response #5551 @​pichlermarc
• fix(instrumentation-http): report stable client metrics response code #9586 @​jtescher
• fix(sdk-node): instantiate baggage processor when env var is set #5634 @​pichlermarc

🏠 Internal

• refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
• refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
  • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
• refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
• test: test Node.js 24 in CI #5661 @​cjihrig

Commits

• 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
• 6803723 fix(deps): update all patch versions (#5685)
• d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
• 56610a0 test: test Node.js 24 in CI (#5661)
• 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
• 373edd9 Revert "fix(sdk-metrics): improve PeriodicExportingMetricReader() constructor...
• 0c21db4 feat(instrumentation-xml-http-request): support migration to stable HTTP semc...
• 0665c85 refactor(sdk-node): update semconv usage to ATTR_ exports (#5668)
• d07d630 refactor(sdk-trace-base): update semconv usage to ATTR_ exports (#5669)
• bc8c94e refactor(sdk-trace-node): update semconv usage to ATTR_ exports (#5670)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-metrics-otlp-proto from 0.200.0 to 0.201.0

Release notes

Sourced from @​opentelemetry/exporter-metrics-otlp-proto's releases.

experimental/v0.201.0

0.201.0

🚀 Features

• feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @​trentm
  • Configure the instrumentation with semconvStabilityOptIn: 'http' to use the new, stable semconv v1.23.1 semantics or 'http/dup' for both old (v1.7.0) and stable semantics. When semconvStabilityOptIn is not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.
• feat(instrumentation): New semconvStabilityFromStr() utility for semconv stability migration in instrumentations. #5684 @​trentm
  • See the utility comment.
• feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @​JamieDanielson
• feat(instrumentation-http): capture synthetic source type on requests #5488 @​JacksonWeber

🐛 Bug Fixes

• fix(otlp-transformer): do not throw when deserializing empty JSON response #5551 @​pichlermarc
• fix(instrumentation-http): report stable client metrics response code #9586 @​jtescher
• fix(sdk-node): instantiate baggage processor when env var is set #5634 @​pichlermarc

🏠 Internal

• refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @​svetlanabrennan
• refactor(instrumentation-http): Add back support for http semconv #5665 @​JamieDanielson
  • Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
• refactor(sdk-node): update semconv usage to ATTR_ exports #5668 @​trentm
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's resource detector setup. #5582 @​beeme1mr
• chore(sdk-node): Refactored using get*FromEnv utility function instead of process.env for NodeSDK's logging setup. #5563 @​weyert
• test: test Node.js 24 in CI #5661 @​cjihrig

Commits

• 4ce5bd1 chore: prepare release 2.0.1/0.201.0 (#5683)
• 6803723 fix(deps): update all patch versions (#5685)
• d4d3732 feat(instrumentation): export generic 'semconvStabilityFromStr()' utility, ra...
• 56610a0 test: test Node.js 24 in CI (#5661)
• 697e1d3 refactor(instrumentation-http): Add back support for http semconv (#5665)
• 373edd9 Revert "fix(sdk-metrics): improve PeriodicExportingMetricReader() constructor...
• 0c21db4 feat(instrumentation-xml-http-request): support migration to stable HTTP semc...
• 0665c85 refactor(sdk-node): update semconv usage to ATTR_ exports (#5668)
• d07d630 refactor(sdk-trace-base): update semconv usage to ATTR_ exports (

[dependabot]

The reviewers field in the dependabot.yml file will be removed soon. Please use the code owners file to specify reviewers for Dependabot PRs. For more information, see this blog post.

[david-luna]

tests are failing for @opentelemetry/instrumentation-fs package. the only change in the new version is an update of the @opentelemetry/instrumentationdependency. https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2828/files#diff-b0c4fd7496f2b42a21f841853dc43e2142501cdbdeb2768b23b6e0b6fd0463f5

[david-luna]

It also includes @opentelemetry/instrumentation-aws-sdk update where support for v2.0 of the SDK is removed

[david-luna]

@dependabot rebase

[david-luna]

From the commit list on the fs instrumentation I cannot by the commit summary if there was a intentional change.

Also the number of spans seems to change between environments
this is the error with node 18.19.0 (run)

not ok 336 should be strictly equal
  ---
    operator: equal
    expected: 18
    actual:   22
    at: Object.checkTelemetry (/home/runner/work/elastic-otel-node/elastic-otel-node/packages/opentelemetry-node/test/instr-fs.test.js:55:15)

this is with the same node version locally

not ok 6 should be strictly equal
  ---
    operator: equal
    expected: 18
    actual:   37    <-- more spans here
    at: Object.checkTelemetry (/Users/david/Documents/repos/el/elastic-otel-node/packages/opentelemetry-node/test/instr-fs.test.js:55:15)

also the use of require/import matters. By doing this change

diff --git a/packages/opentelemetry-node/test/instr-fs.test.js b/packages/opentelemetry-node/test/instr-fs.test.js
index 82a8e31..d2149fe 100644
--- a/packages/opentelemetry-node/test/instr-fs.test.js
+++ b/packages/opentelemetry-node/test/instr-fs.test.js
@@ -34,7 +34,7 @@ const testFixtures = [
         args: ['./fixtures/use-fs.js'],
         cwd: __dirname,
         env: {
-            NODE_OPTIONS: '--require=@elastic/opentelemetry-node',
+            NODE_OPTIONS: '--import=@elastic/opentelemetry-node',
             OTEL_NODE_ENABLED_INSTRUMENTATIONS: 'fs',
         },

the number of spans is being reduced drastically and the error changes to

ok 5 exited successfully: err=null
not ok 6 should be strictly equal
  ---
    operator: equal
    expected: 18
    actual:   3
    at: Object.checkTelemetry (/Users/david/Documents/repos/el/elastic-otel-node/packages/opentelemetry-node/test/instr-fs.test.js:55:15)

and the trace summary looks like this

node ./lib/cli.js -o trace-summary
{"name":"mockotlpserver","level":30,"msg":"OTLP/HTTP listening at http://[::1]:4318/","time":"2025-05-27T09:58:15.845Z"}
{"name":"mockotlpserver","level":30,"msg":"OTLP/gRPC listening at http://localhost:4317/","time":"2025-05-27T09:58:15.851Z"}
------ trace 178891 (1 span) ------
       span 8ee183 "fs realpathSync" (0.5ms, SPAN_KIND_INTERNAL)
------ trace 9e0f89 (2 spans) ------
       span 3d03e6 "manual-span" (0.7ms, SPAN_KIND_INTERNAL)
  +0ms `- span 1dd30d "fs stat" (0.4ms, SPAN_KIND_INTERNAL)

the fixture code only does a fs.stat call so my guess is that somehow the instrumentation is not suppressing internal calls when using require although it shouldn't. I think with import the internal spans are suppressed which is good.

So I plan to:

• change the test to use --import
• update test assertions

cc: @trentm