molo/frontend
Watch
1
Fork
You've already forked frontend
 0
Code Issues 1 Pull requests Packages 1 Wiki Activity Actions

fix(deps): update opentelemetry to v3 - autoclosed #27

Closed
renovate-bot wants to merge 1 commit from renovate/major-opentelemetry into master
pull from: renovate/major-opentelemetry
merge into: molo:master
Conversation 1 Commits 1 Files changed 1 +2 -2
renovate-bot commented 2026-10-28 12:02:53 +01:00
Collaborator
Copy link

This PR contains the following updates:

Package Change Age Confidence
@opentelemetry/resources (source) ^2.12.0 → ^3.0.0 age confidence
@opentelemetry/sdk-trace (source) ^2.12.0 → ^3.0.0 age confidence

Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/resources)

v3.0.0

Compare Source

💥 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
  • 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
    • The Jaeger propagator is deprecated by the OpenTelemetry specification in favour of W3CTraceContextPropagator. Use W3CTraceContextPropagator from @opentelemetry/core instead.
    • See the 3.x migration guide for full instructions.
  • feat(exporter-jaeger)!: remove @opentelemetry/exporter-jaeger package
    • The Jaeger exporter has been removed. Jaeger has deprecated its custom Thrift collection protocols in favor of standard OpenTelemetry Protocol (OTLP). Use standard OTLP exporters instead.
    • See the 3.x migration guide for full instructions.
  • chore!: bump minimum node.js version to >=22.15.0
  • chore(sdk-trace-base, sdk-trace-web)!: remove the @opentelemetry/sdk-trace-base and @opentelemetry/sdk-trace-web packages #​7117
    • The sdk-trace-base, sdk-trace-web, and sdk-trace-node packages have been replaced by the @opentelemetry/sdk-trace package.
      See the 3.x migration guide for full migration instructions.
  • feat!: replace the browser field in package.json with #platform subpath imports #​7141 @​overbalance
    • Resolvers with the node condition load the Node.js build; all others load the browser build. Bundlers without imports support fail; see the migration guide.
    • webpack needs 5.54 or later. Parcel needs package exports enabled and cannot resolve #platform from require().
    • Root type declarations describe the Node.js build.
  • feat(resources)!: remove the ./detectors/platform and ./detectors/platform/browser subpath exports; import from the package root #​7141 @​overbalance
  • feat(core, sdk-trace, sdk-logs, exporter-zipkin)!: remove the ./platform and ./platform/browser subpath exports; import from the package root #​7141 @​overbalance
  • fix(sdk-logs)!: replace LoggerConfig.disabled with enabled to match the specification #​7160
    • Replace disabled: true with enabled: false, and disabled: false with enabled: true. Loggers remain enabled by default.
🚀 Features
  • feat(sdk-metrics): stabilize maxExportBatchSize option in PeriodicExportingMetricReader
  • chore(sdk-logs): mark @opentelemetry/sdk-logs as stable #​7143 @​trentm
  • feat(sdk-trace, sdk-logs): add the browser-only disableAutoFlushOnDocumentHide to BatchSpanProcessorOptions and BatchLogRecordProcessorOptions, deprecate BatchSpanProcessorBrowserOptions and BatchLogRecordProcessorBrowserOptions #​7140 @​overbalance
🐛 Bug Fixes
  • fix(sdk-metrics): guard against a missing or empty name to MeterProvider#getMeter #​7105 @​trentm
  • fix: resolve the ESM build through the default export condition instead of import, so a resolver that activates neither import nor require still finds an entry point #​7132 @​overbalance
  • fix(sdk-trace): make the Node.js RandomIdGenerator id generators prototype methods, so subclasses can override them #​7190 @​overbalance
  • fix(sdk-logs): report a rejected document-hide flush to the global error handler #​7187 @​overbalance
  • fix(sdk-trace): count attributes passed to startSpan toward attributeCountLimit #​7176 @​overbalance
  • fix(resources): stop reading globalThis.process in the browser build #​7173 @​overbalance
  • fix(core): return false instead of undefined from the browser getBooleanFromEnv #​7188 @​overbalance
  • fix(core): no longer drop an attribute value that is an object that has undefined properties #​7207 @​trentm
    • isAnyValue() now returns true for {aStr: 'bob', anUndefined: undefined}. This restores the behavior of the old isLogAttributeValue from version 2.x of the sdk-logs package.
    • "Cleaning" of attributes, by cleanAttributes() and maybeAddAttribute(), will now drop undefined properties from objects. For example, logger.emit(attributes: {myAttr: {aStr: 'bob', anUndefined: undefined}, ...) will include attributes: {myAttr: {aStr: 'bob'}}.
📚 Documentation
  • chore(examples): drop examples/{otlp-exporter-node,grpc-js} #​7096
🏠 Internal
  • chore: remove @opentelemetry/sdk-trace-web package from examples and bundler tests #​7095
  • chore(sdk-trace): add StackContextManager in @opentelemetry/sdk-trace package #​7086
  • feat(ci): support releasing from maintenance branches #​6767 @​pichlermarc
    • The API documentation site is only redeployed for releases whose commit is reachable from main, so a maintenance release no longer overwrites it.
  • chore: don't close stale issues #x @​maryliag
  • chore: mark the workspace root package as private #​7097 @​overbalance
  • chore: declare the Node.js and npm version floors that the tsdown build requires via devEngines #​7093 @​overbalance
    • The migration to tsdown raised the toolchain a contributor needs to build this repo, but nothing declared it. Contributors now build on Node.js ^24.11.1 || >=26.0.0 with npm >=11.10.0; both are advisory and warn rather than fail. The published packages are unaffected and still support Node.js >=22.15.0, which the test matrix continues to cover.
  • test(bundler-tests): typecheck packages under legacy module resolution #​7127 @​overbalance
  • chore: remove the redundant module field from package.json; bundlers resolve the ESM build through the exports map #​7130 @​overbalance
  • test(bundler-tests): bundle the platform packages for iOS and Android with Metro and Expo, and load them under Jest's jsdom environment #​7131 @​overbalance
  • fix(verify-pack): read the npm 12 pack --json output, which is keyed by package name instead of an array #​7133 @​overbalance
  • fix(karma): resolve plugins and the process shim from the repo root, so browser tests run with isolated installs #​7137 @​overbalance
  • fix(nx): key the version target defaults by the target name, so a cache hit restores the generated src/version.ts #​7134 @​overbalance
  • fix(nx): make the test, test:browser and test:webworker targets compile their dependencies first, since tests load dependencies from their dist #​7139 @​overbalance
  • fix(verify-pack): extract tarballs under the root node_modules, so workspace dependencies resolve and entry points load fully instead of being skipped #​7138 @​overbalance
  • build: lint published packages for unused dependencies with knip, as part of npm run lint #​7200 @​overbalance
  • chore(exporter-zipkin): move @opentelemetry/resources to devDependencies, since only tests use it #​7200 @​overbalance
  • build: fail the tsdown build when its output includes a module from outside the package #​7195 @​overbalance
  • refactor(sdk-trace): remove the pagehide listener from the browser BatchSpanProcessor, it was registered on document and never ran, and visibilitychange already flushes on unload #​7153 @​adityareddy-dev
  • refactor(sdk-logs): remove the pagehide listener from the browser BatchLogRecordProcessor, it was registered on document and never ran, and visibilitychange already flushes on unload #​7153 @​adityareddy-dev
  • refactor(sdk-trace, sdk-logs, sdk-metrics): type timers with ReturnType<typeof setTimeout> instead of NodeJS.Timeout #​7174 @​overbalance

Configuration

📅 Schedule: (in timezone Europe/Warsaw)

  • Branch creation
    • Between 09:00 AM and 10:59 PM (* 9-22 * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@opentelemetry/resources](https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-resources) ([source](https://github.com/open-telemetry/opentelemetry-js)) | [`^2.12.0` → `^3.0.0`](https://renovatebot.com/diffs/npm/@opentelemetry%2fresources/2.12.0/3.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@opentelemetry%2fresources/3.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@opentelemetry%2fresources/2.12.0/3.0.0?slim=true) | | [@opentelemetry/sdk-trace](https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/sdk-trace) ([source](https://github.com/open-telemetry/opentelemetry-js)) | [`^2.12.0` → `^3.0.0`](https://renovatebot.com/diffs/npm/@opentelemetry%2fsdk-trace/2.12.0/3.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@opentelemetry%2fsdk-trace/3.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@opentelemetry%2fsdk-trace/2.12.0/3.0.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-js (@&#8203;opentelemetry/resources)</summary> ### [`v3.0.0`](https://github.com/open-telemetry/opentelemetry-js/blob/HEAD/CHANGELOG.md#300) [Compare Source](https://github.com/open-telemetry/opentelemetry-js/compare/v2.12.0...v3.0.0) ##### :boom: Breaking Changes - chore(sdk-trace-node)!: remove the `@opentelemetry/sdk-trace-node` package [#&#8203;7054](https://github.com/open-telemetry/opentelemetry-js/issues/7054) - The sdk-trace-node package has been replaced by the `@opentelemetry/sdk-trace` package. See the [3.x migration guide](doc/3.x/migration-guide.md) for full migration instructions. - chore(shim-opentracing)!: remove the `@opentelemetry/shim-opentracing` package - In the [OpenTelemetry Specification v1.56.0](https://github.com/open-telemetry/opentelemetry-specification/releases/tag/v1.56.0) the [OpenTracing compatibility requirements were deprecated](https://github.com/open-telemetry/opentelemetry-specification/pull/4938). The JavaScript OpenTracing shim package will not receive any more releases after the current [2.12.0 release](https://www.npmjs.com/package/@opentelemetry/shim-opentracing/v/2.12.0) ([source code for last release](https://github.com/open-telemetry/opentelemetry-js/tree/v2.12.0/packages/opentelemetry-shim-opentracing/)). - chore(context-async-hooks)!: remove the unused class `AsyncHooksContextManager` [#&#8203;7078](https://github.com/open-telemetry/opentelemetry-js/pull/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 [#&#8203;6293](https://github.com/open-telemetry/opentelemetry-js/pull/6293) [@&#8203;overbalance](https://github.com/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` [#&#8203;7053](https://github.com/open-telemetry/opentelemetry-js/pull/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` [#&#8203;7057](https://github.com/open-telemetry/opentelemetry-js/pull/7057) - Pass `timeoutMillis` to `provider.forceFlush({ timeoutMillis })` instead. The default timeout is 30000ms. - feat(propagator-jaeger)!: remove `@opentelemetry/propagator-jaeger` package [#&#8203;7077](https://github.com/open-telemetry/opentelemetry-js/pull/7077) - The Jaeger propagator is deprecated by the OpenTelemetry specification in favour of `W3CTraceContextPropagator`. Use `W3CTraceContextPropagator` from `@opentelemetry/core` instead. - See the [3.x migration guide](doc/3.x/migration-guide.md) for full instructions. - feat(exporter-jaeger)!: remove `@opentelemetry/exporter-jaeger` package - The Jaeger exporter has been removed. Jaeger has deprecated its custom Thrift collection protocols in favor of standard OpenTelemetry Protocol (OTLP). Use standard OTLP exporters instead. - See the [3.x migration guide](doc/3.x/migration-guide.md) for full instructions. - chore!: bump minimum node.js version to >=22.15.0 - chore(sdk-trace-base, sdk-trace-web)!: remove the `@opentelemetry/sdk-trace-base` and `@opentelemetry/sdk-trace-web` packages [#&#8203;7117](https://github.com/open-telemetry/opentelemetry-js/issues/7117) - The sdk-trace-base, sdk-trace-web, and sdk-trace-node packages have been replaced by the `@opentelemetry/sdk-trace` package. See the [3.x migration guide](doc/3.x/migration-guide.md) for full migration instructions. - feat!: replace the `browser` field in `package.json` with `#platform` subpath imports [#&#8203;7141](https://github.com/open-telemetry/opentelemetry-js/pull/7141) [@&#8203;overbalance](https://github.com/overbalance) - Resolvers with the `node` condition load the Node.js build; all others load the browser build. Bundlers without `imports` support fail; see the migration guide. - webpack needs 5.54 or later. Parcel needs package exports enabled and cannot resolve `#platform` from `require()`. - Root type declarations describe the Node.js build. - feat(resources)!: remove the `./detectors/platform` and `./detectors/platform/browser` subpath exports; import from the package root [#&#8203;7141](https://github.com/open-telemetry/opentelemetry-js/pull/7141) [@&#8203;overbalance](https://github.com/overbalance) - feat(core, sdk-trace, sdk-logs, exporter-zipkin)!: remove the `./platform` and `./platform/browser` subpath exports; import from the package root [#&#8203;7141](https://github.com/open-telemetry/opentelemetry-js/pull/7141) [@&#8203;overbalance](https://github.com/overbalance) - fix(sdk-logs)!: replace `LoggerConfig.disabled` with `enabled` to match the specification [#&#8203;7160](https://github.com/open-telemetry/opentelemetry-js/issues/7160) - Replace `disabled: true` with `enabled: false`, and `disabled: false` with `enabled: true`. Loggers remain enabled by default. ##### :rocket: Features - feat(sdk-metrics): stabilize `maxExportBatchSize` option in `PeriodicExportingMetricReader` - chore(sdk-logs): mark `@opentelemetry/sdk-logs` as stable [#&#8203;7143](https://github.com/open-telemetry/opentelemetry-js/issues/7143) [@&#8203;trentm](https://github.com/trentm) - feat(sdk-trace, sdk-logs): add the browser-only `disableAutoFlushOnDocumentHide` to `BatchSpanProcessorOptions` and `BatchLogRecordProcessorOptions`, deprecate `BatchSpanProcessorBrowserOptions` and `BatchLogRecordProcessorBrowserOptions` [#&#8203;7140](https://github.com/open-telemetry/opentelemetry-js/pull/7140) [@&#8203;overbalance](https://github.com/overbalance) ##### :bug: Bug Fixes - fix(sdk-metrics): guard against a missing or empty name to MeterProvider#getMeter [#&#8203;7105](https://github.com/open-telemetry/opentelemetry-js/pull/7105) [@&#8203;trentm](https://github.com/trentm) - fix: resolve the ESM build through the `default` export condition instead of `import`, so a resolver that activates neither `import` nor `require` still finds an entry point [#&#8203;7132](https://github.com/open-telemetry/opentelemetry-js/pull/7132) [@&#8203;overbalance](https://github.com/overbalance) - fix(sdk-trace): make the Node.js `RandomIdGenerator` id generators prototype methods, so subclasses can override them [#&#8203;7190](https://github.com/open-telemetry/opentelemetry-js/pull/7190) [@&#8203;overbalance](https://github.com/overbalance) - fix(sdk-logs): report a rejected document-hide flush to the global error handler [#&#8203;7187](https://github.com/open-telemetry/opentelemetry-js/pull/7187) [@&#8203;overbalance](https://github.com/overbalance) - fix(sdk-trace): count attributes passed to `startSpan` toward `attributeCountLimit` [#&#8203;7176](https://github.com/open-telemetry/opentelemetry-js/pull/7176) [@&#8203;overbalance](https://github.com/overbalance) - fix(resources): stop reading `globalThis.process` in the browser build [#&#8203;7173](https://github.com/open-telemetry/opentelemetry-js/pull/7173) [@&#8203;overbalance](https://github.com/overbalance) - fix(core): return `false` instead of `undefined` from the browser `getBooleanFromEnv` [#&#8203;7188](https://github.com/open-telemetry/opentelemetry-js/pull/7188) [@&#8203;overbalance](https://github.com/overbalance) - fix(core): no longer *drop* an attribute value that is an object that has `undefined` properties [#&#8203;7207](https://github.com/open-telemetry/opentelemetry-js/issues/7207) [@&#8203;trentm](https://github.com/trentm) - `isAnyValue()` now returns true for `{aStr: 'bob', anUndefined: undefined}`. This restores the behavior of the old `isLogAttributeValue` from version 2.x of the `sdk-logs` package. - "Cleaning" of attributes, by `cleanAttributes()` and `maybeAddAttribute()`, will now drop undefined properties from objects. For example, `logger.emit(attributes: {myAttr: {aStr: 'bob', anUndefined: undefined}, ...)` will include `attributes: {myAttr: {aStr: 'bob'}}`. ##### :books: Documentation - chore(examples): drop examples/{otlp-exporter-node,grpc-js} [#&#8203;7096](https://github.com/open-telemetry/opentelemetry-js/pull/7096) ##### :house: Internal - chore: remove `@opentelemetry/sdk-trace-web` package from examples and bundler tests [#&#8203;7095](https://github.com/open-telemetry/opentelemetry-js/pull/7095) - chore(sdk-trace): add `StackContextManager` in `@opentelemetry/sdk-trace` package [#&#8203;7086](https://github.com/open-telemetry/opentelemetry-js/pull/7086) - feat(ci): support releasing from maintenance branches [#&#8203;6767](https://github.com/open-telemetry/opentelemetry-js/issues/6767) [@&#8203;pichlermarc](https://github.com/pichlermarc) - The API documentation site is only redeployed for releases whose commit is reachable from `main`, so a maintenance release no longer overwrites it. - chore: don't close stale issues [#x](https://github.com/open-telemetry/opentelemetry-js/issues/x) [@&#8203;maryliag](https://github.com/maryliag) - chore: mark the workspace root package as private [#&#8203;7097](https://github.com/open-telemetry/opentelemetry-js/pull/7097) [@&#8203;overbalance](https://github.com/overbalance) - chore: declare the Node.js and npm version floors that the tsdown build requires via `devEngines` [#&#8203;7093](https://github.com/open-telemetry/opentelemetry-js/pull/7093) [@&#8203;overbalance](https://github.com/overbalance) - The migration to tsdown raised the toolchain a contributor needs to build this repo, but nothing declared it. Contributors now build on Node.js `^24.11.1 || >=26.0.0` with npm `>=11.10.0`; both are advisory and warn rather than fail. The published packages are unaffected and still support Node.js `>=22.15.0`, which the test matrix continues to cover. - test(bundler-tests): typecheck packages under legacy module resolution [#&#8203;7127](https://github.com/open-telemetry/opentelemetry-js/pull/7127) [@&#8203;overbalance](https://github.com/overbalance) - chore: remove the redundant `module` field from `package.json`; bundlers resolve the ESM build through the `exports` map [#&#8203;7130](https://github.com/open-telemetry/opentelemetry-js/pull/7130) [@&#8203;overbalance](https://github.com/overbalance) - test(bundler-tests): bundle the platform packages for iOS and Android with Metro and Expo, and load them under Jest's jsdom environment [#&#8203;7131](https://github.com/open-telemetry/opentelemetry-js/pull/7131) [@&#8203;overbalance](https://github.com/overbalance) - fix(verify-pack): read the npm 12 `pack --json` output, which is keyed by package name instead of an array [#&#8203;7133](https://github.com/open-telemetry/opentelemetry-js/pull/7133) [@&#8203;overbalance](https://github.com/overbalance) - fix(karma): resolve plugins and the `process` shim from the repo root, so browser tests run with isolated installs [#&#8203;7137](https://github.com/open-telemetry/opentelemetry-js/pull/7137) [@&#8203;overbalance](https://github.com/overbalance) - fix(nx): key the `version` target defaults by the target name, so a cache hit restores the generated `src/version.ts` [#&#8203;7134](https://github.com/open-telemetry/opentelemetry-js/pull/7134) [@&#8203;overbalance](https://github.com/overbalance) - fix(nx): make the `test`, `test:browser` and `test:webworker` targets compile their dependencies first, since tests load dependencies from their `dist` [#&#8203;7139](https://github.com/open-telemetry/opentelemetry-js/pull/7139) [@&#8203;overbalance](https://github.com/overbalance) - fix(verify-pack): extract tarballs under the root `node_modules`, so workspace dependencies resolve and entry points load fully instead of being skipped [#&#8203;7138](https://github.com/open-telemetry/opentelemetry-js/pull/7138) [@&#8203;overbalance](https://github.com/overbalance) - build: lint published packages for unused dependencies with knip, as part of `npm run lint` [#&#8203;7200](https://github.com/open-telemetry/opentelemetry-js/pull/7200) [@&#8203;overbalance](https://github.com/overbalance) - chore(exporter-zipkin): move `@opentelemetry/resources` to `devDependencies`, since only tests use it [#&#8203;7200](https://github.com/open-telemetry/opentelemetry-js/pull/7200) [@&#8203;overbalance](https://github.com/overbalance) - build: fail the tsdown build when its output includes a module from outside the package [#&#8203;7195](https://github.com/open-telemetry/opentelemetry-js/pull/7195) [@&#8203;overbalance](https://github.com/overbalance) - refactor(sdk-trace): remove the `pagehide` listener from the browser `BatchSpanProcessor`, it was registered on `document` and never ran, and `visibilitychange` already flushes on unload [#&#8203;7153](https://github.com/open-telemetry/opentelemetry-js/pull/7153) [@&#8203;adityareddy-dev](https://github.com/adityareddy-dev) - refactor(sdk-logs): remove the `pagehide` listener from the browser `BatchLogRecordProcessor`, it was registered on `document` and never ran, and `visibilitychange` already flushes on unload [#&#8203;7153](https://github.com/open-telemetry/opentelemetry-js/pull/7153) [@&#8203;adityareddy-dev](https://github.com/adityareddy-dev) - refactor(sdk-trace, sdk-logs, sdk-metrics): type timers with `ReturnType<typeof setTimeout>` instead of `NodeJS.Timeout` [#&#8203;7174](https://github.com/open-telemetry/opentelemetry-js/pull/7174) [@&#8203;overbalance](https://github.com/overbalance) </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Warsaw) - Branch creation - Between 09:00 AM and 10:59 PM (`* 9-22 * * *`) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC44MS4wIiwidXBkYXRlZEluVmVyIjoiNDQuODEuMCIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
fix(deps): update opentelemetry to v3
Some checks failed
renovate/stability-days Updates have met minimum release age requirement
Details
renovate/artifacts Artifact file update failure
/ build (push) Failing after -3s
Details
/ test-components (push) Failing after -5s
Details
/ test-e2e (push) Failing after -6s
Details
/ push (push) Has been skipped
Details
7cdb9972ea
renovate-bot commented 2026-10-28 12:02:53 +01:00
Author
Collaborator
Copy link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: molo-frontend@0.0.0
npm error Found: @opentelemetry/api@1.9.1
npm error node_modules/@opentelemetry/api
npm error   @opentelemetry/api@"^1.9.1" from the root project
npm error   @opentelemetry/api@"^1.3.0" from @opentelemetry/api-logs@0.223.0
npm error   node_modules/@opentelemetry/api-logs
npm error     @opentelemetry/api-logs@"0.223.0" from @opentelemetry/instrumentation@0.223.0
npm error     node_modules/@opentelemetry/instrumentation
npm error       @opentelemetry/instrumentation@"^0.223.0" from @opentelemetry/auto-instrumentations-web@0.68.0
npm error       node_modules/@opentelemetry/auto-instrumentations-web
npm error         @opentelemetry/auto-instrumentations-web@"^0.68.0" from the root project
npm error       4 more (@opentelemetry/instrumentation-document-load, ...)
npm error   11 more (@opentelemetry/auto-instrumentations-web, ...)
npm error
npm error Could not resolve dependency:
npm error @opentelemetry/resources@"^3.0.0" from the root project
npm error
npm error Conflicting peer dependency: @opentelemetry/api@1.10.0
npm error node_modules/@opentelemetry/api
npm error   peer @opentelemetry/api@">=1.10.0 <1.11.0" from @opentelemetry/resources@3.0.0
npm error   node_modules/@opentelemetry/resources
npm error     @opentelemetry/resources@"^3.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-10-28T11_02_50_704Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-10-28T11_02_50_704Z-debug-0.log
### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: molo-frontend@0.0.0 npm error Found: @opentelemetry/api@1.9.1 npm error node_modules/@opentelemetry/api npm error @opentelemetry/api@"^1.9.1" from the root project npm error @opentelemetry/api@"^1.3.0" from @opentelemetry/api-logs@0.223.0 npm error node_modules/@opentelemetry/api-logs npm error @opentelemetry/api-logs@"0.223.0" from @opentelemetry/instrumentation@0.223.0 npm error node_modules/@opentelemetry/instrumentation npm error @opentelemetry/instrumentation@"^0.223.0" from @opentelemetry/auto-instrumentations-web@0.68.0 npm error node_modules/@opentelemetry/auto-instrumentations-web npm error @opentelemetry/auto-instrumentations-web@"^0.68.0" from the root project npm error 4 more (@opentelemetry/instrumentation-document-load, ...) npm error 11 more (@opentelemetry/auto-instrumentations-web, ...) npm error npm error Could not resolve dependency: npm error @opentelemetry/resources@"^3.0.0" from the root project npm error npm error Conflicting peer dependency: @opentelemetry/api@1.10.0 npm error node_modules/@opentelemetry/api npm error peer @opentelemetry/api@">=1.10.0 <1.11.0" from @opentelemetry/resources@3.0.0 npm error node_modules/@opentelemetry/resources npm error @opentelemetry/resources@"^3.0.0" from the root project npm error npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-10-28T11_02_50_704Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-10-28T11_02_50_704Z-debug-0.log ```
renovate-bot changed title from fix(deps): update opentelemetry to v3 to fix(deps): update opentelemetry to v3 - autoclosed 2026-11-08 03:01:47 +01:00
renovate-bot closed this pull request 2026-11-08 03:01:47 +01:00
Some checks failed
renovate/stability-days Updates have met minimum release age requirement
Details
renovate/artifacts Artifact file update failure
/ build (push) Failing after -3s
Details
/ test-components (push) Failing after -5s
Details
/ test-e2e (push) Failing after -6s
Details
/ push (push) Has been skipped
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
molo/frontend!27
No description provided.