[dependabot]

Bumps the minor-patch group with 3 updates in the /packages/squad-sdk directory: @opentelemetry/exporter-metrics-otlp-grpc, @opentelemetry/exporter-trace-otlp-grpc and @opentelemetry/sdk-node.

Updates @opentelemetry/exporter-metrics-otlp-grpc from 0.223.1 to 0.301.0

Release notes

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

experimental/v0.301.0

0.301.0

💥 Breaking Changes

• feat(sdk-node)!: The experimental startNodeSdk() code path for environment-based config (i.e. when not using a config file), has full option coverage. #6999 @​trentm
  • startNodeSdk() should now be a viable replacement for new NodeSDK(), supporting similar (but not exactly the same) options for configuring most SDK components.
  • startNodeSDK() has been deprecated, use startNodeSdk() (slight capitalization change).
  • Two resource detectors have been added to the default set for new NodeSDK() users: os and serviceinstance. This means that when not specifying OTEL_NODE_RESOURCE_DETECTORS, the SDK Resource will include os.* and service.instance.id attributes.
• refactor(configuration)!: The responsibility of the configuration package has been reduced to just the parsing, validation, and TypeScript types for declarative config files. #6999 @​trentm
  • Breaking: The configuration package no longer supports creating a synthetic ConfigurationModel from environment variables.
  • Breaking: The configuration package API has changed: createConfigFactory() has been replaced with `parseConfigFile().

🐛 Bug Fixes

• fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (#7261) @​avens19
• fix(otlp-grpc-exporter-base): avoid an incomplete mTLS warning for root-CA-only TLS configuration (#7235) @​LarryHu0217
• fix(sdk-node): warn and skip, instead of erroring, on an unknown resource detector name in declarative config #7252 @​trentm
• fix(sdk-node): use OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT and OTEL_LINK_ATTRIBUTE_COUNT_LIMIT environment variables for span limits #6999 @​trentm
  • Before this change, different environment variable names (see next point), that are not in the OTel spec were used. They will still be supported as a fallback for the spec names for a period of approximately six months.
  • The OTEL_SPAN_ATTRIBUTE_PER_EVENT_COUNT_LIMIT and OTEL_SPAN_ATTRIBUTE_PER_LINK_COUNT_LIMIT environment variables are deprecated. Support for them will be removed sometime after six months, to allow transition to the correct environment variables in the spec.
• fix(otlp-exporter-base): pick the browser fetch mode from the document origin, so exports from an opaque-origin document (e.g. a sandboxed iframe) no longer fail with mode: 'same-origin' #7211 @​MO2k4
• fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @​volodymyrshk @​pichlermarc
  • Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
  • If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.

📚 Documentation

• docs(exporters): update dead semantic conventions resource specification links in OTLP exporters #7254 @​helmipradita

experimental/v0.300.0

0.300.0

Summary

• The minimum supported Node.js has been raised to >=22.15.0. This means that support for Node.js 18 and 20 has been dropped.
• The public interface has changed
  • for notes on migrating to 3.x / 0.300.x see the upgrade guide
• Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

• chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated. The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release (source code for last release).
• feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
  • The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name. Remove it from any setConfig() or constructor call.
• feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor, metricReader, spanProcessor and deprecated namespace re-exports node, tracing
  • NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
  • NodeSDKConfiguration.metricReader — use metricReaders instead.

... (truncated)

Commits

• 9985264 chore: prepare next release (#7272)
• 7983f1c fix: raise @​opentelemetry/api peer floor to 1.10.0 where needed (#7259)
• 0a5c4ed chore(deps): update dependency lerna to v10.1.1 (#7270)
• 4eda691 fix(propagator-b3): reject invalid trace id lengths (#7262)
• 5ca48a7 fix(context-zone): declare the @​opentelemetry/api peer dependency (#7268)
• babaf15 docs(migration): note that API 1.10.0 needs SDK 3.x (#7253)
• daae704 fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (...
• cc2a315 fix(otlp-grpc-exporter-base): avoid false mTLS configuration warnings (#7241)
• 29eec06 fix(sdk-node): warn and skip, instead of erroring, on an unknown resource det...
• 4667c0a docs: update dead semantic conventions resource specification links (#7254)
• Additional commits viewable in compare view

Updates @opentelemetry/exporter-trace-otlp-grpc from 0.223.1 to 0.301.0

Release notes

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

experimental/v0.301.0

0.301.0

💥 Breaking Changes

• feat(sdk-node)!: The experimental startNodeSdk() code path for environment-based config (i.e. when not using a config file), has full option coverage. #6999 @​trentm
  • startNodeSdk() should now be a viable replacement for new NodeSDK(), supporting similar (but not exactly the same) options for configuring most SDK components.
  • startNodeSDK() has been deprecated, use startNodeSdk() (slight capitalization change).
  • Two resource detectors have been added to the default set for new NodeSDK() users: os and serviceinstance. This means that when not specifying OTEL_NODE_RESOURCE_DETECTORS, the SDK Resource will include os.* and service.instance.id attributes.
• refactor(configuration)!: The responsibility of the configuration package has been reduced to just the parsing, validation, and TypeScript types for declarative config files. #6999 @​trentm
  • Breaking: The configuration package no longer supports creating a synthetic ConfigurationModel from environment variables.
  • Breaking: The configuration package API has changed: createConfigFactory() has been replaced with `parseConfigFile().

🐛 Bug Fixes

• fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (#7261) @​avens19
• fix(otlp-grpc-exporter-base): avoid an incomplete mTLS warning for root-CA-only TLS configuration (#7235) @​LarryHu0217
• fix(sdk-node): warn and skip, instead of erroring, on an unknown resource detector name in declarative config #7252 @​trentm
• fix(sdk-node): use OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT and OTEL_LINK_ATTRIBUTE_COUNT_LIMIT environment variables for span limits #6999 @​trentm
  • Before this change, different environment variable names (see next point), that are not in the OTel spec were used. They will still be supported as a fallback for the spec names for a period of approximately six months.
  • The OTEL_SPAN_ATTRIBUTE_PER_EVENT_COUNT_LIMIT and OTEL_SPAN_ATTRIBUTE_PER_LINK_COUNT_LIMIT environment variables are deprecated. Support for them will be removed sometime after six months, to allow transition to the correct environment variables in the spec.
• fix(otlp-exporter-base): pick the browser fetch mode from the document origin, so exports from an opaque-origin document (e.g. a sandboxed iframe) no longer fail with mode: 'same-origin' #7211 @​MO2k4
• fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @​volodymyrshk @​pichlermarc
  • Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
  • If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.

📚 Documentation

• docs(exporters): update dead semantic conventions resource specification links in OTLP exporters #7254 @​helmipradita

experimental/v0.300.0

0.300.0

Summary

• The minimum supported Node.js has been raised to >=22.15.0. This means that support for Node.js 18 and 20 has been dropped.
• The public interface has changed
  • for notes on migrating to 3.x / 0.300.x see the upgrade guide
• Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

• chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated. The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release (source code for last release).
• feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
  • The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name. Remove it from any setConfig() or constructor call.
• feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor, metricReader, spanProcessor and deprecated namespace re-exports node, tracing
  • NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
  • NodeSDKConfiguration.metricReader — use metricReaders instead.

... (truncated)

Commits

• 9985264 chore: prepare next release (#7272)
• 7983f1c fix: raise @​opentelemetry/api peer floor to 1.10.0 where needed (#7259)
• 0a5c4ed chore(deps): update dependency lerna to v10.1.1 (#7270)
• 4eda691 fix(propagator-b3): reject invalid trace id lengths (#7262)
• 5ca48a7 fix(context-zone): declare the @​opentelemetry/api peer dependency (#7268)
• babaf15 docs(migration): note that API 1.10.0 needs SDK 3.x (#7253)
• daae704 fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (...
• cc2a315 fix(otlp-grpc-exporter-base): avoid false mTLS configuration warnings (#7241)
• 29eec06 fix(sdk-node): warn and skip, instead of erroring, on an unknown resource det...
• 4667c0a docs: update dead semantic conventions resource specification links (#7254)
• Additional commits viewable in compare view

Updates @opentelemetry/sdk-node from 0.223.1 to 0.301.0

Release notes

Sourced from @​opentelemetry/sdk-node's releases.

experimental/v0.301.0

0.301.0

💥 Breaking Changes

• feat(sdk-node)!: The experimental startNodeSdk() code path for environment-based config (i.e. when not using a config file), has full option coverage. #6999 @​trentm
  • startNodeSdk() should now be a viable replacement for new NodeSDK(), supporting similar (but not exactly the same) options for configuring most SDK components.
  • startNodeSDK() has been deprecated, use startNodeSdk() (slight capitalization change).
  • Two resource detectors have been added to the default set for new NodeSDK() users: os and serviceinstance. This means that when not specifying OTEL_NODE_RESOURCE_DETECTORS, the SDK Resource will include os.* and service.instance.id attributes.
• refactor(configuration)!: The responsibility of the configuration package has been reduced to just the parsing, validation, and TypeScript types for declarative config files. #6999 @​trentm
  • Breaking: The configuration package no longer supports creating a synthetic ConfigurationModel from environment variables.
  • Breaking: The configuration package API has changed: createConfigFactory() has been replaced with `parseConfigFile().

🐛 Bug Fixes

• fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (#7261) @​avens19
• fix(otlp-grpc-exporter-base): avoid an incomplete mTLS warning for root-CA-only TLS configuration (#7235) @​LarryHu0217
• fix(sdk-node): warn and skip, instead of erroring, on an unknown resource detector name in declarative config #7252 @​trentm
• fix(sdk-node): use OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT and OTEL_LINK_ATTRIBUTE_COUNT_LIMIT environment variables for span limits #6999 @​trentm
  • Before this change, different environment variable names (see next point), that are not in the OTel spec were used. They will still be supported as a fallback for the spec names for a period of approximately six months.
  • The OTEL_SPAN_ATTRIBUTE_PER_EVENT_COUNT_LIMIT and OTEL_SPAN_ATTRIBUTE_PER_LINK_COUNT_LIMIT environment variables are deprecated. Support for them will be removed sometime after six months, to allow transition to the correct environment variables in the spec.
• fix(otlp-exporter-base): pick the browser fetch mode from the document origin, so exports from an opaque-origin document (e.g. a sandboxed iframe) no longer fail with mode: 'same-origin' #7211 @​MO2k4
• fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @​volodymyrshk @​pichlermarc
  • Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
  • If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.

📚 Documentation

• docs(exporters): update dead semantic conventions resource specification links in OTLP exporters #7254 @​helmipradita

experimental/v0.300.0

0.300.0

Summary

• The minimum supported Node.js has been raised to >=22.15.0. This means that support for Node.js 18 and 20 has been dropped.
• The public interface has changed
  • for notes on migrating to 3.x / 0.300.x see the upgrade guide
• Only stable versions 3.0.0 are compatible with this release

💥 Breaking Changes

• chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
  • In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated. The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release (source code for last release).
• feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
  • The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name. Remove it from any setConfig() or constructor call.
• feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor, metricReader, spanProcessor and deprecated namespace re-exports node, tracing
  • NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
  • NodeSDKConfiguration.metricReader — use metricReaders instead.

... (truncated)

Commits

• 9985264 chore: prepare next release (#7272)
• 7983f1c fix: raise @​opentelemetry/api peer floor to 1.10.0 where needed (#7259)
• 0a5c4ed chore(deps): update dependency lerna to v10.1.1 (#7270)
• 4eda691 fix(propagator-b3): reject invalid trace id lengths (#7262)
• 5ca48a7 fix(context-zone): declare the @​opentelemetry/api peer dependency (#7268)
• babaf15 docs(migration): note that API 1.10.0 needs SDK 3.x (#7253)
• daae704 fix(instrumentation-http): don't require('forwarded-parse') in ESM builds (...
• cc2a315 fix(otlp-grpc-exporter-base): avoid false mTLS configuration warnings (#7241)
• 29eec06 fix(sdk-node): warn and skip, instead of erroring, on an unknown resource det...
• 4667c0a docs: update dead semantic conventions resource specification links (#7254)
• Additional commits viewable in compare view

[bradygaster]

@dependabot rebase

[dependabot]

Dependabot couldn't access the repository. Because of this, Dependabot cannot update this pull request.

[Copilot]

🟡 Changes recommended

The dependency upgrade is missing from the lockfile, breaks configured telemetry through removed SDK APIs, and requires a higher Node.js version than the package declares.

3 open issues

• Regenerate and commit the root lockfile · New
• Update telemetry imports and metricReaders for SDK 0.300.0 · New
• Align the Node.js engine floor with SDK 0.300.0 · New

What changed in this PR

Updates the Squad SDK’s optional OpenTelemetry dependencies used for tracing and metrics export.

Changes:

• Bumps the OTLP gRPC metrics and trace exporters from ^0.223.0 to ^0.300.0.
• Bumps @opentelemetry/sdk-node to ^0.300.0, without changing telemetry initialization or the root lockfile.

File	Description
packages/​squad-sdk/​package.json	Updates three optional OpenTelemetry dependency ranges.

_{Review effort: Balanced (auto)}

[bradygaster]

Dependency triage: holding this update. The three 0.301.x OTel packages are not synchronized into the root workspace lockfile (npm ci fails with missing 0.301.0/3.1.0 packages). The proposed SDK generation also requires a coordinated API/signal-package and Node engine review; the currently published SDK advertises Node >=22.5.0. I am not bypassing peer resolution or broadening runtime support policy to make CI green. Keep the compatible 0.223.x generation until that coordinated upgrade is validated.