Repository navigation
ci: bump opentelemetry to 1.45.2 for CVE-2026-126360 - #316
Conversation
Regenerated with the lock's own uv command and --upgrade-package for the opentelemetry set only, so the universal Windows stanzas and markers that dependabot's regeneration dropped in #313 stay intact. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Imran Siddique <45405841+imran-siddique@users.noreply.github.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
The differential job runs pip-audit over experiments/a2a-tck/environment.txt, which carried its own 1.45.1 pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Imran Siddique <45405841+imran-siddique@users.noreply.github.com>
dinakarjs
left a comment
There was a problem hiding this comment.
Reviewed 1648f7e against base 7f68cc5. Across requirements/dev.txt, requirements/agt.txt and experiments/a2a-tck/environment.txt, all content outside the intended OpenTelemetry requirement/hash entries is identical. API/SDK/semantic-conventions move together where present; existing universal platform/Python markers remain. git diff --check passes.
Independent Linux/Python 3.12.14 with pip 26.2.2: clean --dry-run --ignore-installed resolution passes for dev (with --require-hashes) and the TCK environment. AGT's hash-checked --no-deps dry run also passes, matching its isolated CI installer contract. Ordinary dependency resolution for AGT fails on both the base and this head because toolkit-core 4.1.0 declares cryptography<49 while the lock pins 50.0.1. That is the pre-existing, explicitly documented requirements/agt-overrides.txt policy, not an OpenTelemetry regression; I do not describe that lock as ordinarily dependency-consistent.
Current-head hosted CI 43664654401 passes the six Python 3.11/3.12/3.13 Linux/Windows jobs (including security scans and installed dependency checks) and isolated governance; TCK differential 43664654345 and CodeQL pass. No local runtime-suite rerun or new hardware claim. No blocking finding in this bounded update. Prepared with OpenAI Codex.
|
@rajnisht7 @carloshvp could one of you review this by November 17? It clears CVE-2026-126360 in opentelemetry-api, which fails the Security scan step on about 20 open PRs here, and as my own PR it needs an approval from someone else. |
opentelemetry-api1.45.1 has CVE-2026-126360 (fixed in 1.45.2), which fails theSecurity scanstep on open PRs in this repo.Regenerated
requirements/dev.txtandrequirements/agt.txtwith their header commands plus--upgrade-packagefor the opentelemetry packages only: api, sdk and semantic-conventions move together, nothing else changes. #313 carries the same bump inside a 19-package group whose regeneration strips environment markers (for exampleaiologic ; python_full_version < '3.13'andcffi ; platform_python_implementation != 'PyPy'), so it stays out of this fix.experiments/a2a-tck/environment.txthad its ownopentelemetry-api==1.45.1, which thedifferentialjob audits; the second commit moves it to 1.45.2. The environment resolves on Linux 3.12 with every other pin unchanged.🤖 Generated with Claude Code