Repository navigation
Conversation
…e lock (CVE-2026-114603) pip-audit in the quality job flags opentelemetry-api 1.42.1 with CVE-2026-114603 (fixed in 1.45.1), so quality has been red on main since 5f49fbb. The opentelemetry packages pin one another exactly, so the family moves together: api, sdk, proto and the OTLP exporters 1.42.1 -> 1.45.1, instrumentation and semantic-conventions 0.63b1 -> 0.66b1, plus two packages the 1.45 exporters now need (opentelemetry-exporter-http-transport, -otlp-common 0.66b1). arize-phoenix-otel moves 0.16.1 -> 0.17.2 with them: 0.16.1 reads the exporter's private _headers, which 1.45 removed, so phoenix.otel.register raised and PROMETHEUS_TRACING never started. 0.17.2 requires opentelemetry-exporter-otlp-proto-http>=1.45.0. A real span sent through prometheus.tracing.phoenix to a loopback OTLP collector arrives with the new lock (and with the old one; it failed with only the otel bump). All of it is in the evals extra only: the base install, the Mac app's extras and the Docker image do not carry opentelemetry. Locked with uv 0.11.3 so the lock stays revision 3 and nothing else moves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
OAraLabs
pushed a commit
that referenced
this pull request
Oct 23, 2026
…es (CVE-2026-114603) The quality job's pip-audit step fails on main (opentelemetry-api 1.42.1, CVE-2026-114603, fixed in 1.45.1), so it fails every PR. #844 is the fix; this is the identical uv.lock change so this PR's check can go green. It is the same bytes as #844, so whichever merges second is a no-op. Verified: pip-audit on the exported lock reports no known vulnerabilities; ruff and the mypy gate were already clean; the purge tests pass on the bumped lock. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UjrXNciMTQJ8Ms46sH4fu
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.
Why
Main's
qualityjob is red. Its pip-audit step flags opentelemetry-api 1.42.1 with CVE-2026-114603, which is fixed in 1.45.1. Main has failed this way since 5f49fbb (run 39841872693, and again at 763e76d, run 39868039364), so every open PR shows the same red check, #843 included.What changes (
uv.lockonly)api,sdk,proto,exporter-otlp,exporter-otlp-proto-common/-grpc/-http. These packages pin one another exactly, so the api cannot move on its own.instrumentationandsemantic-conventions, 0.63b1 → 0.66b1.opentelemetry-exporter-http-transportandopentelemetry-exporter-otlp-common, both 0.66b1.arize-phoenix-otel0.16.1 → 0.17.2. This is not optional:_headers, which 1.45 removed.phoenix.otel.registerraises'HTTPSpanExporter' object has no attribute '_headers', soPROMETHEUS_TRACING=1silently never starts.opentelemetry-exporter-otlp-proto-http>=1.45.0.The lock was made with a targeted
uv lock --upgrade-package …using uv 0.11.3. That keepsrevision = 3, and the diff is one contiguous block of opentelemetry entries plus the arize-phoenix-otel entry. uv 0.13.0 would have rewritten the file as revision 5 and reordered markers, so it wasn't used.Who is affected: everything here is in the
evalsextra only. The base install, the Mac app's extras (mcp slack discord discovery) and the Docker image's extras (mcp slack discord push) export no opentelemetry package.Verified
uv export --all-extrasthenpip-audit --no-deps): No known vulnerabilities found.uv lock --checkpasses.--frozenfrom this lock with theevalsextra:prometheus.tracing.phoenix.init_tracingagainst it, emitted a span withspan_context, and calledshutdown_tracing.POST /v1/traces, protobuf). Main's lock passes the same check.tests/test_evals.py,test_extras_security_floors.py,test_web_is_base.py,test_honest_status_notes.pyandtest_template_key_placement.pyin that environment: 126 passed.🤖 Generated with Claude Code