feat(deps): Bump OpenTelemetry dependencies#19682
Open
andreiborza wants to merge 1 commit intodevelopfrom
Open
feat(deps): Bump OpenTelemetry dependencies#19682andreiborza wants to merge 1 commit intodevelopfrom
andreiborza wants to merge 1 commit intodevelopfrom
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
andreiborza
force-pushed
the
ab/bump-otel
branch
from
4755ff2 to
3f4d8da
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Contributor
size-limit report 📦
|
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
andreiborza
force-pushed
the
ab/bump-otel
branch
2 times, most recently
from
b6f42a9 to
03df6e6
Compare
Bump OpenTelemetry instrumentation packages: - @opentelemetry/instrumentation-amqplib: 0.52.0 → 0.54.0 - @opentelemetry/instrumentation-connect: 0.53.0 → 0.55.0 - @opentelemetry/instrumentation-dataloader: 0.26.0 → 0.28.0 - @opentelemetry/instrumentation-express: 0.53.0 → 0.55.0 - @opentelemetry/instrumentation-fastify: 0.53.0 → 0.55.0 - @opentelemetry/instrumentation-fs: 0.29.0 → 0.31.0 - @opentelemetry/instrumentation-generic-pool: 0.53.0 → 0.55.0 - @opentelemetry/instrumentation-graphql: 0.47.0 → 0.49.0 - @opentelemetry/instrumentation-hapi: 0.55.0 → 0.57.0 - @opentelemetry/instrumentation-http: 0.57.0 → 0.59.0 - @opentelemetry/instrumentation-ioredis: 0.57.0 → 0.59.0 - @opentelemetry/instrumentation-kafkajs: 0.27.0 → 0.29.0 - @opentelemetry/instrumentation-knex: 0.54.0 → 0.56.0 - @opentelemetry/instrumentation-koa: 0.57.0 → 0.59.0 - @opentelemetry/instrumentation-lru-memoizer: 0.54.0 → 0.56.0 - @opentelemetry/instrumentation-mongodb: 0.52.0 → 0.54.0 - @opentelemetry/instrumentation-mongoose: 0.55.0 → 0.57.0 - @opentelemetry/instrumentation-mysql: 0.55.0 → 0.57.0 - @opentelemetry/instrumentation-mysql2: 0.55.0 → 0.57.0 - @opentelemetry/instrumentation-nestjs-core: 0.57.0 → 0.59.0 - @opentelemetry/instrumentation-pg: 0.51.0 → 0.53.0 - @opentelemetry/instrumentation-redis-4: 0.56.0 → 0.58.0 - @opentelemetry/instrumentation-tedious: 0.28.0 → 0.30.0 - @opentelemetry/instrumentation-undici: 0.20.0 → 0.22.0 - @opentelemetry/instrumentation-aws-sdk: 0.66.0 → 0.68.0 - @opentelemetry/instrumentation: 0.57.0 → 0.59.0 Bump OpenTelemetry core packages: - @opentelemetry/api: 1.9.0 → 1.10.0 - @opentelemetry/core: 1.30.0 → 1.32.0 - @opentelemetry/sdk-trace-base: 1.30.0 → 1.32.0 - @opentelemetry/resources: 1.30.0 → 1.32.0 - @opentelemetry/context-async-hooks: 1.30.0 → 1.32.0 - @opentelemetry/semantic-conventions: ^1.39.0 → ^1.40.0 Bump other packages: - import-in-the-middle: ^2.0.6 → ^3.0.0 - @fastify/otel: 0.16.0 → 0.17.1 - @prisma/instrumentation: 7.2.0 → 7.4.2 Add yarn resolution for @opentelemetry/instrumentation to 0.213.0 to prevent @prisma/instrumentation (^0.207.0) and @fastify/otel (^0.212.0) from pulling in older versions with conflicting import-in-the-middle copies, which breaks ESM HTTP instrumentation. Update tests for instrumentation-undici 0.22.0 spec compliance: - Remove http.response.header.content-length assertions Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Agent transcript: https://claudescope.sentry.dev/share/O05-QsJWR3lOK245mwX-27Gq-pIQH7U34EagqOeyR4w
andreiborza
force-pushed
the
ab/bump-otel
branch
from
03df6e6 to
50b6d6d
Compare
JPeer264
approved these changes
Mar 9, 2026
| { key: 'network.peer.address', value: { stringValue: expect.any(String) } }, | ||
| { key: 'network.peer.port', value: { intValue: 3030 } }, | ||
| { key: 'http.response.status_code', value: { intValue: 200 } }, | ||
| { key: 'http.response.header.content-length', value: { intValue: 16 } }, |
Member
There was a problem hiding this comment.
l: This got dropped on purpose? According to this page we could use http.response.body.size instead (that is also true for other files where this got dropped)
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.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Closes #19683 (added automatically)