security: vulnerability remediation - #323
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9787bed. Configure here.
| go.opentelemetry.io/otel/sdk/metric v1.38.0 | ||
| go.opentelemetry.io/otel/trace v1.38.0 | ||
| go.opentelemetry.io/otel/sdk/metric v1.40.0 | ||
| go.opentelemetry.io/otel/trace v1.40.0 |
There was a problem hiding this comment.
OTel bump breaks resource merge
High Severity
The go.opentelemetry.io/otel/sdk update to v1.40.0 introduces a schema version conflict. resource.Default() now uses semconv/1.39.0, but lib/otel/otel.go still merges attributes with semconv/1.37.0. This ErrSchemaURLConflict prevents the API from initializing and starting up.
Reviewed by Cursor Bugbot for commit 9787bed. Configure here.


Vulnerability Remediation
Fixed
Not Included
Deferred details
Note
Low Risk
Lockfile-only semver bumps on observability dependencies; no logic changes, though OTLP/trace/metric behavior should be smoke-tested if OTel is enabled in production.
Overview
Bumps OpenTelemetry core modules from v1.38.0 to v1.40.0 (
otel,metric,sdk,sdk/metric,trace) andgolang.org/x/sysfrom v0.38.0 to v0.40.0, with matchinggo.sumentries. There are no application code changes—only dependency manifests.This is aimed at GHSA-9h8m-3fm2-qjrq on
go.opentelemetry.io/otel/sdk. OTel is used whenotel.enabledis on (HTTP viaotelchi, manual spans on WebSocket exec/cp paths inlib/oteland API handlers).Reviewed by Cursor Bugbot for commit 9787bed. Bugbot is set up for automated code reviews on this repo. Configure here.