fix(deps): bump OpenTelemetry experimental packages to ^0.219.0 (consumer-facing vuln)#1014
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (16)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (11)
📝 WalkthroughWalkthroughThis PR updates OpenTelemetry instrumentation dependencies from ChangesOpenTelemetry Instrumentation Package Version Alignment
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/instrumentation-vertexai/src/aiplatform-instrumentation.ts`:
- Line 105: The wrapper functions declare their rest parameter incorrectly as
`...args: any`; update the signatures to `...args: any[]` so the rest parameter
is typed as an array/tuple; specifically change the wrapper signature `function
method(this: any, ...args: any)` in the aiplatform instrumentation (and the
analogous wrapper `method` signatures in the qdrant, cohere, and bedrock
instrumentation files) to `function method(this: any, ...args: any[])`, keeping
all other logic unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 79b4e005-4967-49e1-bbe0-f40bb8eed703
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (16)
packages/instrumentation-anthropic/package.jsonpackages/instrumentation-bedrock/package.jsonpackages/instrumentation-chromadb/package.jsonpackages/instrumentation-cohere/package.jsonpackages/instrumentation-google-generativeai/package.jsonpackages/instrumentation-langchain/package.jsonpackages/instrumentation-llamaindex/package.jsonpackages/instrumentation-mcp/package.jsonpackages/instrumentation-openai/package.jsonpackages/instrumentation-pinecone/package.jsonpackages/instrumentation-qdrant/package.jsonpackages/instrumentation-together/package.jsonpackages/instrumentation-vertexai/package.jsonpackages/instrumentation-vertexai/src/aiplatform-instrumentation.tspackages/sample-app/package.jsonpackages/traceloop-sdk/package.json
doronkopit5
force-pushed
the
dk/fix-dependabot-vulns
branch
from
47fe042 to
2574de6
Compare
Addresses the high-severity advisory in @opentelemetry/sdk-node
(<0.217.0, Prometheus exporter crash) — the only Dependabot critical/high
that reaches consumers of the published packages, since the lockfile is
not published and consumer installs re-resolve declared ranges. Pinned to
the latest experimental line (0.219.0) rather than the minimum patch
(0.217.0) so consumers stay current.
- Bump @opentelemetry/{sdk-node,instrumentation,exporter-trace-otlp-proto}
from ^0.203.0 to ^0.219.0 across all packages, coordinated to avoid two
copies of @opentelemetry/instrumentation in a consumer's tree.
- Bump esbuild ^0.25.7 -> ^0.28.1 (traceloop-sdk devDependency) to clear a
new high advisory (Deno binary integrity bypass, patched in 0.28.1).
Build-only; not in any published package's production closure.
- Raise production dependency floors to patched versions: lodash ^4.18.1
(instrumentation-llamaindex) and uuid ^11.1.1 (traceloop-sdk).
- vertexai: simplify wrapperMethod arg typing to `...args: any[]` (it
previously over-specified the predict overload union) because
@opentelemetry/instrumentation tightened _wrap's wrapper types;
runtime behavior is unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
doronkopit5
force-pushed
the
dk/fix-dependabot-vulns
branch
from
2574de6 to
e30216d
Compare
doronkopit5
changed the title
nina-kollman
approved these changes
Jun 16, 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.
Solves #1013
Summary
Addresses Dependabot critical/high alerts with a focus on consumer safety — ensuring nobody who
npm installs the published@traceloop/*packages inherits a vulnerable dependency. Refreshed from a fresh sweep on 2026-06-15 (branch is current withmain).The key finding
Of the 5 critical + 60 high open alerts, only one has ever reached consumers in an unfixed state:
@opentelemetry/sdk-node(high — Prometheus exporter crash), declared^0.203.0onmain(patch is0.217.0, out of range). This PR moves it — and the rest of the OTel experimental set — to the latest line,0.219.0.Everything else is either:
npm installresolves to a fixed version (e.g.protobufjsviagoogle-gax,langsmithvia@langchain/core). Only this repo's (unpublished) lockfile showed the old versions.handlebars,convict,fast-xml-parser) and remaining highs (axios,undici,tar,rollup,langsmithinsample-app, …) arrive solely through test SDKs, build/release tooling, or theprivatesample-app. They are never in any published package's production closure.Why so few matter: the lockfile isn't published and
pnpm.overridesonly affect this repo — consumer safety is governed solely by the declareddependenciesranges in publishedpackage.jsonfiles.Changes
^0.203.0→^0.219.0(latest) for@opentelemetry/sdk-node,@opentelemetry/instrumentation, and@opentelemetry/exporter-trace-otlp-protoacross all packages. The coordination prevents two copies of@opentelemetry/instrumentationin a consumer's tree. (Note:^0.217.0would have cleared the vuln, but for0.xranges caret caps at<0.218.0; pinning the latest line keeps consumers current.)esbuilddevDependency bump^0.25.7→^0.28.1(traceloop-sdk) — clears a newly-filed high advisory (Deno binary integrity bypass, patched 0.28.1). Build-only, not in any consumer's production closure, so zero consumer-runtime impact; bumped to keep the dashboard clean.lodash ^4.18.1(instrumentation-llamaindex),uuid ^11.1.1(traceloop-sdk).instrumentation-vertexaitype fix:@opentelemetry/instrumentationtightened the typing of_wrap's wrapper argument, which conflicted with vertexai's explicitly-typedwrapperMethod. Simplified its signature tofunction method(this: any, ...args: any[])and dropped the now-unusedgoogle-gaxtype import. Runtime behavior is unchanged (type-only adjustment); re-confirmed at 0.219.0.Verification
pnpm nx run-many -t build— all 17 projects build (confirms the vertexai type fix still holds at 0.219.0).pnpm nx run-many -t test— all suites pass exceptinstrumentation-qdrant, which fails locally only withECONNREFUSED 127.0.0.1:6333(its tests require a live Qdrant server, provided by the CI service container — pre-existing/environmental, unchanged by this PR).@opentelemetry/{sdk-node,instrumentation,exporter-trace-otlp-proto}resolve to a single0.219.0;esbuildresolves to0.28.1;lodash/uuidresolve to patched.Out of scope (intentionally)
Dev/build-only and auto-fixable lockfile alerts (other than the trivial
esbuildfloor) were not chased — they don't reach consumers, and clearing them would mean eitherpnpm.overrideschurn or a full lockfile regeneration for no consumer benefit.Summary by CodeRabbit
Summary by CodeRabbit