Repository navigation
security: bump multidict, opentelemetry-api (MODERATE GHSAs) - #7
Conversation
Lockfile-only update; no pyproject.toml changes (all packages are transitive). - multidict 6.7.1 -> 6.9.1 (GHSA-54p9-h82j-f925). Held on the 6.x line rather than jumping to 7.x. - opentelemetry-api 1.42.1 -> 1.45.2 (GHSA-xcq7-p3pf-p88h). The otel siblings pulled in by daytona move with it because they pin api/semconv exactly: sdk, proto, exporter-otlp-proto-{common,http} -> 1.45.2; semantic-conventions, instrumentation, instrumentation-aiohttp-client, util-http -> 0.66b2; new required deps exporter-http-transport and exporter-otlp-common 0.66b2. zeroconf is not bumped: libp2p 0.6.0 requires zeroconf<0.148.0 and the first fixed zeroconf (0.149.x) needs libp2p 0.7.0. torch, numpy, setuptools, virtualenv and libp2p are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 1
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Summary
Lockfile-only security update (
uv.lock); nopyproject.tomlchanges. All affected packages are transitive.daytona(devextra). It stays on the 6.x line instead of moving to 7.x.daytona(devextra). Its otel siblings move with it because they pin the api version exactly: sdk, proto, and exporter-otlp-proto-{common,http} go to 1.45.2; semantic-conventions, instrumentation, instrumentation-aiohttp-client, and util-http go to 0.66b2. exporter-http-transport and exporter-otlp-common 0.66b2 are new, required deps of exporter-otlp-proto-http 1.45.2.pip install -e ".[dev]"doesn't useuv.lockand already installs fixed multidict/otel versions. This PR brings the uv lock in line with that.Not fixed: zeroconf (blocked by libp2p)
zeroconf 0.147.4 has five MODERATE advisories: GHSA-9663-mqmp-p9mm (fixed 0.149.12), GHSA-9pgc-3ccv-5297 (0.149.5), GHSA-phvx-9mgw-67r5 (0.149.6), GHSA-qc2x-6f54-m6h9 (0.149.16), and GHSA-rfg2-pjw2-56x2 (0.149.7). libp2p 0.6.0 requires
zeroconf>=0.147.0,<0.148.0; the first libp2p that allows a fixed zeroconf is 0.7.0 (zeroconf>=0.149.16,<0.151.0). Fixing zeroconf therefore needs a libp2p upgrade, which is out of scope here.Watch items
Verification
In the locked env (
uv sync --locked --extra dev):ruff check: passruff format --check: pass (118 files)mypy src scripts: pass (63 files)pytest tests: 343 passedpip-auditonuv export --all-extras: multidict and opentelemetry-api findings cleared, no new findings. Remaining findings are pre-existing and out of scope (zeroconf, libp2p, setuptools, torch, virtualenv).All advisories verified on GitHub Advisory DB and OSV. Signed commit 2fecf6f. Separate from #5.