feat(opentelemetry-node): update deps matching "@opentelemetry/*"#1388
Merged
feat(opentelemetry-node): update deps matching "@opentelemetry/*"#1388
Conversation
- opentelemetry-js release: open-telemetry/opentelemetry-js#6464 - opentelemetry-js-contrib release: open-telemetry/opentelemetry-js-contrib#3410 (Though *most* of the updates there are just for updating their opentelemetry-js deps, so it is difficult to separate out the actual changes.) Summary of changes: 0.8.3 -> 0.8.4 @opentelemetry/resource-detector-container 0.10.0 -> 0.11.0 @opentelemetry/instrumentation-openai (range-bump) 0.20.0 -> 0.21.0 @opentelemetry/resource-detector-azure (range-bump) 0.21.0 -> 0.22.0 @opentelemetry/instrumentation-kafkajs (range-bump) 0.22.0 -> 0.23.0 @opentelemetry/instrumentation-undici (range-bump) 0.22.0 -> 0.23.0 @opentelemetry/winston-transport (range-bump) 0.25.0 -> 0.26.0 @opentelemetry/instrumentation-runtime-node (range-bump) 0.27.0 -> 0.29.0 @opentelemetry/instrumentation-cucumber (range-bump) 0.29.0 -> 0.30.0 @opentelemetry/instrumentation-dataloader (range-bump) 0.31.0 -> 0.32.0 @opentelemetry/instrumentation-fs (range-bump) 0.31.0 -> 0.32.0 @opentelemetry/instrumentation-tedious (range-bump) 0.33.2 -> 0.33.3 @opentelemetry/resource-detector-alibaba-cloud 0.37.0 -> 0.38.0 @opentelemetry/instrumentation-oracledb (range-bump) 0.38.2 -> 0.38.3 @opentelemetry/host-metrics 0.47.0 -> 0.48.0 @opentelemetry/resource-detector-gcp (range-bump) 0.55.0 -> 0.56.0 @opentelemetry/instrumentation-connect (range-bump) 0.55.0 -> 0.56.0 @opentelemetry/instrumentation-dns (range-bump) 0.55.0 -> 0.56.0 @opentelemetry/instrumentation-generic-pool (range-bump) 0.55.0 -> 0.56.0 @opentelemetry/instrumentation-memcached (range-bump) 0.56.0 -> 0.57.0 @opentelemetry/instrumentation-fastify (range-bump) 0.56.0 -> 0.57.0 @opentelemetry/instrumentation-knex (range-bump) 0.56.0 -> 0.57.0 @opentelemetry/instrumentation-lru-memoizer (range-bump) 0.56.0 -> 0.57.0 @opentelemetry/instrumentation-net (range-bump) 0.56.0 -> 0.57.0 @opentelemetry/instrumentation-router (range-bump) 0.56.0 -> 0.57.0 @opentelemetry/instrumentation-winston (range-bump) 0.57.0 -> 0.58.0 @opentelemetry/instrumentation-bunyan (range-bump) 0.57.0 -> 0.58.0 @opentelemetry/instrumentation-cassandra-driver (range-bump) 0.57.0 -> 0.58.0 @opentelemetry/instrumentation-restify (range-bump) 0.58.0 -> 0.59.0 @opentelemetry/instrumentation-hapi (range-bump) 0.58.0 -> 0.59.0 @opentelemetry/instrumentation-mongoose (range-bump) 0.58.0 -> 0.59.0 @opentelemetry/instrumentation-mysql (range-bump) 0.58.0 -> 0.59.0 @opentelemetry/instrumentation-mysql2 (range-bump) 0.58.0 -> 0.59.0 @opentelemetry/instrumentation-nestjs-core (range-bump) 0.58.0 -> 0.59.0 @opentelemetry/instrumentation-pino (range-bump) 0.58.0 -> 0.60.0 @opentelemetry/instrumentation-socket.io (range-bump) 0.59.0 -> 0.60.0 @opentelemetry/instrumentation-amqplib (range-bump) 0.59.0 -> 0.61.0 @opentelemetry/instrumentation-graphql (range-bump) 0.60.0 -> 0.61.0 @opentelemetry/instrumentation-express (range-bump) 0.60.0 -> 0.61.0 @opentelemetry/instrumentation-ioredis (range-bump) 0.60.0 -> 0.61.0 @opentelemetry/instrumentation-koa (range-bump) 0.60.0 -> 0.61.0 @opentelemetry/instrumentation-redis (range-bump) 0.64.0 -> 0.65.0 @opentelemetry/instrumentation-pg (range-bump) 0.65.0 -> 0.66.0 @opentelemetry/instrumentation-mongodb (range-bump) 0.67.0 -> 0.68.0 @opentelemetry/instrumentation-aws-sdk (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/exporter-logs-otlp-grpc (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/exporter-logs-otlp-http (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/exporter-logs-otlp-proto (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/exporter-metrics-otlp-grpc (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/exporter-metrics-otlp-http (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/exporter-metrics-otlp-proto (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/instrumentation-grpc (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/instrumentation-http (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/sampler-composite (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/sdk-logs (range-bump) 0.212.0 -> 0.213.0 @opentelemetry/sdk-node (range-bump) 1.39.0 -> 1.40.0 @opentelemetry/semantic-conventions 2.5.1 -> 2.6.0 @opentelemetry/core (exact-ver-bump) 2.5.1 -> 2.6.0 @opentelemetry/resources (exact-ver-bump) 2.5.1 -> 2.6.0 @opentelemetry/sdk-metrics (exact-ver-bump) 2.12.0 -> 2.13.0 @opentelemetry/resource-detector-aws
trentm
changed the title
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis pull request bumps multiple dependency versions in packages/opentelemetry-node/package.json (OpenTelemetry core, SDKs, OTLP exporters, instrumentations, resource detectors, sampler, and related packages). It removes two exported functions from packages/opentelemetry-node/hook.mjs: ✨ Finishing Touches
🧪 Generate unit tests (beta)
Comment |
…entation Having the same *single* IITM install in the node_modules tree is necessary for hooking when using IITM's createAddHookMessageChannel() feature.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/opentelemetry-node/hook.mjs (1)
1-12:⚠️ Potential issue | 🟠 MajorLint is currently merge-blocking.
Pipeline reports Prettier failure (Line 1 context). Please run formatter and commit the result so required lint passes.
As per coding guidelines, "Keep reviews short: flag only issues that make the PR unsafe to merge."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/opentelemetry-node/hook.mjs` around lines 1 - 12, Run the code formatter (Prettier) on this module and commit the formatted file so the lint pipeline passes; specifically reformat the top-of-file comment and import/export block that contain the named imports/exports (initialize, resolve, load) to match project Prettier rules (e.g., spacing and newline conventions) and then add the formatted file to the commit.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@packages/opentelemetry-node/hook.mjs`:
- Around line 1-12: Run the code formatter (Prettier) on this module and commit
the formatted file so the lint pipeline passes; specifically reformat the
top-of-file comment and import/export block that contain the named
imports/exports (initialize, resolve, load) to match project Prettier rules
(e.g., spacing and newline conventions) and then add the formatted file to the
commit.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 98cbe0fc-10d0-4c03-ad62-49e118993099
⛔ Files ignored due to path filters (1)
packages/opentelemetry-node/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
packages/opentelemetry-node/hook.mjspackages/opentelemetry-node/package.json
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/opentelemetry-node/hook.mjs`:
- Around line 7-8: The PR removed the named exports getFormat and getSource from
the public module hook.mjs which can break consumers; restore compatibility by
re-exporting getFormat and getSource from packages/opentelemetry-node/hook.mjs
(alongside initialize, resolve, load) or add shims that forward those symbols to
their implementations, and ensure package.json versioning and CHANGELOG/README
note the intentional breaking change if you prefer to remove them; locate
references to these symbols in internal code (search for getFormat/getSource)
and update or keep exports accordingly so runtime imports do not fail.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: b5c75fc0-88f8-49b7-92b1-7b0b75b7f377
📒 Files selected for processing (1)
packages/opentelemetry-node/hook.mjs
…nstr-http with the fix for that
david-luna
approved these changes
Mar 5, 2026
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
2 participants
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.
(Though most of the updates there are just for updating their
opentelemetry-js deps, so it is difficult to separate out the
actual changes.)
Summary of changes: