[dependabot]

Bumps @opentelemetry/sdk-logs from 0.223.0 to 3.1.0.

Release notes

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

v3.1.0

3.1.0

🚀 Features

• feat(resources): Deprecate envDetector in favor of separate resourceAttributesEnvDetector and serviceNameEnvDetector. Also mark serviceInstanceIdDetector as stable (the service.instance.id semconv attribute is now stable). #6999 @​trentm

🐛 Bug Fixes

• fix(context-zone): declare the @opentelemetry/api peer dependency so Yarn PnP can resolve it for context-zone-peer-dep #7268 @​Vivek1898
• fix(core): accept attribute values with shared (non-circular) object references #7068 @​rajanpanth
• 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.
• fix(propagator-b3): reject trace ids that are not 16 or 32 characters long #7262 @​adityareddy-dev

📚 Documentation

• docs(resources): update dead semantic conventions resource specification links #7254 @​helmipradita
• docs(migration): note that @opentelemetry/api v1.10.0 needs SDK 3.x #7253 @​adityareddy-dev

🏠 Internal

• perf(sdk-logs, sdk-trace): wait for each distinct pending resource once per batch instead of once per record #7208 @​shehjaddev
• ci: update the W3C harness for Python 3.14 #7236 @​adityareddy-dev

v3.0.0

3.0.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 experimental versions 0.300.0 are compatible with this release

💥 Breaking Changes

• chore(sdk-trace-node)!: remove the @opentelemetry/sdk-trace-node package #7054
  • The sdk-trace-node package has been replaced by the @opentelemetry/sdk-trace package. See the 3.x migration guide for full migration instructions.
• chore(shim-opentracing)!: remove the @opentelemetry/shim-opentracing package
  • In the OpenTelemetry Specification v1.58.0 the OpenTracing compatibility requirements were deprecated. The JavaScript OpenTracing shim package will not receive any more releases after the current 2.11.0 release (source code for last release).
• chore(context-async-hooks)!: remove the unused class AsyncHooksContextManager #7078
• feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
  • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
  • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/core/build/src/... or @opentelemetry/core/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
  • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
  • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.

... (truncated)

Changelog

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

3.1.0

🚀 Features

• feat(resources): Deprecate envDetector in favor of separate resourceAttributesEnvDetector and serviceNameEnvDetector. Also mark serviceInstanceIdDetector as stable (the service.instance.id semconv attribute is now stable). #6999 @​trentm

🐛 Bug Fixes

• fix(context-zone): declare the @opentelemetry/api peer dependency so Yarn PnP can resolve it for context-zone-peer-dep #7268 @​Vivek1898
• fix(core): accept attribute values with shared (non-circular) object references #7068 @​rajanpanth
• 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.
• fix(propagator-b3): reject trace ids that are not 16 or 32 characters long #7262 @​adityareddy-dev

📚 Documentation

• docs(resources): update dead semantic conventions resource specification links #7254 @​helmipradita
• docs(migration): note that @opentelemetry/api v1.10.0 needs SDK 3.x #7253 @​adityareddy-dev

🏠 Internal

• perf(sdk-logs, sdk-trace): wait for each distinct pending resource once per batch instead of once per record #7208 @​shehjaddev
• ci: update the W3C harness for Python 3.14 #7236 @​adityareddy-dev

3.0.0

💥 Breaking Changes

• chore(sdk-trace-node)!: remove the @opentelemetry/sdk-trace-node package #7054
  • The sdk-trace-node package has been replaced by the @opentelemetry/sdk-trace package. See the 3.x migration guide for full migration instructions.
• chore(shim-opentracing)!: remove the @opentelemetry/shim-opentracing package
  • In the OpenTelemetry Specification v1.56.0 the OpenTracing compatibility requirements were deprecated. The JavaScript OpenTracing shim package will not receive any more releases after the current 2.12.0 release (source code for last release).
• chore(context-async-hooks)!: remove the unused class AsyncHooksContextManager #7078
• feat!: migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @​overbalance
  • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
  • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/core/build/src/... or @opentelemetry/core/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
  • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
  • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
  • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
  • If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
• feat(core)!: remove deprecated getTimeOrigin, otperformance, _globalThis, and unrefTimer from @opentelemetry/core #7053
  • getTimeOrigin() — use performance.timeOrigin directly.
  • otperformance — use the global performance object directly.
  • _globalThis — use globalThis directly.
  • unrefTimer(timer) — call timer.unref() directly in your own code.
• feat(sdk-trace)!: remove deprecated TracerProviderOptions.forceFlushTimeoutMillis #7057
  • Pass timeoutMillis to provider.forceFlush({ timeoutMillis }) instead. The default timeout is 30000ms.
• feat(propagator-jaeger)!: remove @opentelemetry/propagator-jaeger package #7077

... (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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)