Skip to content

chore: upgrade dependencies - #282

Merged
horsefacts merged 5 commits into
mainfrom
pyramid/upgrade-dependencies-2026-11
Nov 14, 2026
Merged

horsefacts merged 5 commits into
mainfrom
pyramid/upgrade-dependencies-2026-11

Conversation

@horsefacts

Copy link
Copy Markdown
Contributor

Versions introduced

  • hono 4.13.13 → 4.13.17
  • opentelemetry-api 1.45.1 → 1.45.2
  • opentelemetry-sdk 1.45.1 → 1.45.2
  • opentelemetry-instrumentation 0.66b1 → 0.66b2
  • opentelemetry-instrumentation-aiohttp-client 0.66b1 → 0.66b2
  • opentelemetry-semantic-conventions 0.66b1 → 0.66b2
  • opentelemetry-util-http 0.66b1 → 0.66b2

Validation pending at publication.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This is a lockfile-only patch bump of hono and the OpenTelemetry Python packages.

What was reviewed:

  • hono 4.13.13 to 4.13.17 in shared/tempo/verifier/package-lock.json. The new version still satisfies the existing ranges in the lockfile (^4.11.4, >=4.12.25, ^4 || ^5.0.0-0).
  • The OpenTelemetry api/sdk (1.45.2) and instrumentation/semconv/util-http (0.66b2) entries in uv.lock. They moved together, so the sdk/instrumentation pins on semantic-conventions stay consistent. The dependency lists did not change.
  • The exporter/proto packages that were not bumped (1.45.1 / 0.66b1) still pair with sdk 1.45.2 within the same 1.45.x patch line. I checked this by reading the lockfile only. I didn't run uv lock --check, npm ci or the repo's check scripts.
Extended reasoning...

The change touches only two lockfiles, shared/tempo/verifier/package-lock.json and uv.lock, with 21 lines changed each way. Every change is a version, URL, hash, size or upload-time update, and no manifest or source file changes. It touches no security-sensitive surface beyond the usual supply-chain trust in pinned registry hashes. I approved because these are patch-level bumps within existing semver ranges, no CODEOWNERS file covers these paths, and there are no other reviewers or open objections on the PR.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This is a mechanical dependency bump plus a regenerated image ref.

What was reviewed:

  • The new agent and verifier tags in config/tasks.yaml share the same source hash (cc1bff2f...). All 132 regenerated Dockerfiles use the matching role: agent-source in environment/ and verifier-source in tests/. The old aad32243 tag no longer appears anywhere in the tree.
  • The lockfiles change only patch versions: hono 4.13.13 to 4.13.17 in the verifier, and OpenTelemetry 1.45.1 to 1.45.2 and 0.66b1 to 0.66b2 in uv.lock. Task prompts, fixtures and verifier code are untouched. The dataset.toml digests are refreshed in the same change, as AGENTS.md requires.
  • I did not rebuild the images or recompute the digests to confirm they match.
Extended reasoning...

The change touches config/tasks.yaml, two lockfiles, four dataset.toml manifests and 132 auto-generated task Dockerfiles. Each Dockerfile changes only its FROM line. It touches no security-sensitive surface (auth, crypto, data handling) beyond routine third-party patch upgrades. I approved because the diff is fully mechanical and every change is consistent with the single source of truth in config/tasks.yaml. There is no CODEOWNERS file and no outstanding reviewer objection in the timeline.

@horsefacts
horsefacts merged commit d5d9e27 into main Nov 14, 2026
10 checks passed
@horsefacts
horsefacts deleted the pyramid/upgrade-dependencies-2026-11 branch November 14, 2026 01:36
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.

1 participant