Repository navigation
Update opentelemetry-js monorepo to v3 - #1021
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
renovate
Bot
force-pushed
the
renovate/major-opentelemetry-js-monorepo
branch
10 times, most recently
from
October 30, 2026 16:16
23be7e3 to
d090898
Compare
renovate
Bot
force-pushed
the
renovate/major-opentelemetry-js-monorepo
branch
10 times, most recently
from
November 6, 2026 18:35
f1baf58 to
54860df
Compare
renovate
Bot
force-pushed
the
renovate/major-opentelemetry-js-monorepo
branch
7 times, most recently
from
November 8, 2026 22:50
89e133d to
18b93e9
Compare
renovate
Bot
force-pushed
the
renovate/major-opentelemetry-js-monorepo
branch
5 times, most recently
from
November 10, 2026 23:37
61c0149 to
8904880
Compare
renovate
Bot
force-pushed
the
renovate/major-opentelemetry-js-monorepo
branch
from
November 11, 2026 15:48
8904880 to
208fce3
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.12.0→3.1.02.12.0→3.1.0Release Notes
open-telemetry/opentelemetry-js (@opentelemetry/core)
v3.1.0Compare Source
🚀 Features
envDetectorin favor of separateresourceAttributesEnvDetectorandserviceNameEnvDetector. Also markserviceInstanceIdDetectoras stable (theservice.instance.idsemconv attribute is now stable). #6999 @trentm🐛 Bug Fixes
@opentelemetry/apipeer dependency so Yarn PnP can resolve it forcontext-zone-peer-dep#7268 @Vivek1898@opentelemetry/apipeer dependency version to 1.10.0 for packages that depend on@opentelemetry/core,@opentelemetry/otlp-transformeror@opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @volodymyrshk @pichlermarc@opentelemetry/api1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.@opentelemetry/apito 1.10.0 or later.📚 Documentation
@opentelemetry/apiv1.10.0 needs SDK 3.x #7253 @adityareddy-dev🏠 Internal
v3.0.0Compare Source
💥 Breaking Changes
@opentelemetry/sdk-trace-nodepackage #7054@opentelemetry/sdk-tracepackage.See the 3.x migration guide for full migration instructions.
@opentelemetry/shim-opentracingpackageAsyncHooksContextManager#7078tsctotsdown, emitting dual CJS/ESM output from a singledist/directory and declaring anexportsmap on every package #6293 @overbalanceexportsmap.exportsmap is an allowlist that Node.js and bundlers enforce, so specifiers such as@opentelemetry/core/build/src/...or@opentelemetry/core/build/esm/...now fail withERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.build/src(CJS),build/esmandbuild/esnext(ESM) intodist/, using.cjs/.mjsextensions with matching.d.cts/.d.mtsdeclarations.<package>/package.jsonis no longer importable for the same reason. Read a package's version from your own dependency metadata, or useSDK_INFOfrom@opentelemetry/corefor the SDK version.esnextentry point has been removed; tools that preferred it fall back tomodule(ESM) ormain(CJS).getTimeOrigin,otperformance,_globalThis, andunrefTimerfrom@opentelemetry/core#7053getTimeOrigin()— useperformance.timeOrigindirectly.otperformance— use the globalperformanceobject directly._globalThis— useglobalThisdirectly.unrefTimer(timer)— calltimer.unref()directly in your own code.TracerProviderOptions.forceFlushTimeoutMillis#7057timeoutMillistoprovider.forceFlush({ timeoutMillis })instead. The default timeout is 30000ms.@opentelemetry/propagator-jaegerpackage #7077W3CTraceContextPropagator. UseW3CTraceContextPropagatorfrom@opentelemetry/coreinstead.@opentelemetry/exporter-jaegerpackage@opentelemetry/sdk-trace-baseand@opentelemetry/sdk-trace-webpackages #7117@opentelemetry/sdk-tracepackage.See the 3.x migration guide for full migration instructions.
browserfield inpackage.jsonwith#platformsubpath imports #7141 @overbalancenodecondition load the Node.js build; all others load the browser build. Bundlers withoutimportssupport fail; see the migration guide.#platformfromrequire()../detectors/platformand./detectors/platform/browsersubpath exports; import from the package root #7141 @overbalance./platformand./platform/browsersubpath exports; import from the package root #7141 @overbalanceLoggerConfig.disabledwithenabledto match the specification #7160disabled: truewithenabled: false, anddisabled: falsewithenabled: true. Loggers remain enabled by default.🚀 Features
maxExportBatchSizeoption inPeriodicExportingMetricReader@opentelemetry/sdk-logsas stable #7143 @trentmdisableAutoFlushOnDocumentHidetoBatchSpanProcessorOptionsandBatchLogRecordProcessorOptions, deprecateBatchSpanProcessorBrowserOptionsandBatchLogRecordProcessorBrowserOptions#7140 @overbalance🐛 Bug Fixes
defaultexport condition instead ofimport, so a resolver that activates neitherimportnorrequirestill finds an entry point #7132 @overbalanceRandomIdGeneratorid generators prototype methods, so subclasses can override them #7190 @overbalancestartSpantowardattributeCountLimit#7176 @overbalanceglobalThis.processin the browser build #7173 @overbalancefalseinstead ofundefinedfrom the browsergetBooleanFromEnv#7188 @overbalanceundefinedproperties #7207 @trentmisAnyValue()now returns true for{aStr: 'bob', anUndefined: undefined}. This restores the behavior of the oldisLogAttributeValuefrom version 2.x of thesdk-logspackage.cleanAttributes()andmaybeAddAttribute(), will now drop undefined properties from objects. For example,logger.emit(attributes: {myAttr: {aStr: 'bob', anUndefined: undefined}, ...)will includeattributes: {myAttr: {aStr: 'bob'}}.📚 Documentation
🏠 Internal
@opentelemetry/sdk-trace-webpackage from examples and bundler tests #7095StackContextManagerin@opentelemetry/sdk-tracepackage #7086main, so a maintenance release no longer overwrites it.devEngines#7093 @overbalance^24.11.1 || >=26.0.0with 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.modulefield frompackage.json; bundlers resolve the ESM build through theexportsmap #7130 @overbalancepack --jsonoutput, which is keyed by package name instead of an array #7133 @overbalanceprocessshim from the repo root, so browser tests run with isolated installs #7137 @overbalanceversiontarget defaults by the target name, so a cache hit restores the generatedsrc/version.ts#7134 @overbalancetest,test:browserandtest:webworkertargets compile their dependencies first, since tests load dependencies from theirdist#7139 @overbalancenode_modules, so workspace dependencies resolve and entry points load fully instead of being skipped #7138 @overbalancenpm run lint#7200 @overbalance@opentelemetry/resourcestodevDependencies, since only tests use it #7200 @overbalancepagehidelistener from the browserBatchSpanProcessor, it was registered ondocumentand never ran, andvisibilitychangealready flushes on unload #7153 @adityareddy-devpagehidelistener from the browserBatchLogRecordProcessor, it was registered ondocumentand never ran, andvisibilitychangealready flushes on unload #7153 @adityareddy-devReturnType<typeof setTimeout>instead ofNodeJS.Timeout#7174 @overbalancev2.12.1Compare Source
2.12.1
🐛 Bug Fixes
host.id@trentmConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.