Skip to content

Update opentelemetry-api for a new security advisory - #130

Merged
github-actions[bot] merged 1 commit into
mainfrom
claude/bump-opentelemetry
Nov 16, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
claude/bump-opentelemetry

Conversation

@acarchidi

Copy link
Copy Markdown
Owner

What changed

  • The security check found one new published problem: opentelemetry-api 1.45.1 (CVE-2026-126360, fixed in 1.45.2). This updates the lockfile to 1.45.2. Only uv.lock changes (8 lines).

How it was tested

  • pip-audit --strict on the updated lockfile: "No known vulnerabilities found". CI runs the full suite.

Risks

  • Low. One patch-level version bump.

Needed from the owner

  • Nothing.

Checkpoint


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017BpEZ7pADxYXWW2RSSarAJ
@github-actions

Copy link
Copy Markdown
Contributor

Claude review: passed

This change moves one supporting library, opentelemetry-api, up one small step (1.45.1 to 1.45.2) to fix a published security problem. Only the lockfile changes. No other package in the lockfile requires the old version. No secrets, tests, checks, or rules are touched, and the description matches the change.

Optional

  • uv.lock:2: The lockfile's format marker drops from revision = 5 to revision = 3. This most likely means an older uv tool wrote the file. The description does not mention it. CI's uv sync --locked will show whether the current uv accepts the file. If CI passes, the next lock done with a newer uv may change this line back, which is harmless but makes noise. Regenerating with the same uv version CI uses would keep the marker at 5.

@github-actions

Copy link
Copy Markdown
Contributor

Overseer: no problems found

From the check on this pull request.

This pull request changes one library's version in the project's version-pinning file, to fix a published security problem. The AGENTS.md dependency-hygiene rule covers this kind of upkeep, so it is not new roadmap work, and it touches no owner-only files. The description matches the change. CI was still running when it was checked.

Notes

  • The lockfile header also changes from "revision = 5" to "revision = 3". This usually means an older uv version rewrote the file. The description does not mention it. It is harmless if CI's locked install accepts it; if CI complains, regenerate the lockfile with the uv version CI uses.
  • Pull request ADR 0055: first issue without the remaining facts; weekly hand-off steps #129 carries the same lockfile change. Whichever merges first, the other should merge cleanly or need only a trivial merge from main.
  • Not a roadmap item and not an owner-path change, so it does not count toward the three-item limit.

A blocking finding counts like a blocking review comment: fix it, or explain on this pull request why not, and the owner settles it (ADR 0019).

@github-actions
github-actions Bot merged commit 4f87947 into main Nov 16, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants