Repository navigation
build: bump claude-agent-sdk 0.2.110 -> 0.2.128 - #93
Merged
Merged
Conversation
Deliberate, isolated bump per issue #44's own convention — bump the harness in an explicit commit, not folded into unrelated work. Only possible to do with any confidence now that #86 (CI), #88 (lockfile), #89 (bundled-CLI understanding), #90/#91 (lint/type gates) all exist: there was previously nothing to test a harness bump against. Read the SDK's changelog for every version between 0.2.111 and 0.2.128 before bumping, not just the target version's entry. Nothing in the documented breaking changes touches this codebase's surface: - 0.2.126's ResultMessage.model_usage type change (dict[str, Any] -> dict[str, ModelUsage]) — grepped for `model_usage` anywhere in orchestrator/config: zero hits. - 0.2.121's --resume/--session-id flag format change — grepped for `resume`/`session_id`: zero hits. - 0.2.124's Windows security hardening — irrelevant, the image is python:3.12-slim on Linux exclusively. Bundled CLI moves 2.1.191 -> 2.1.220 as a side effect (claude-agent-sdk ships its own CLI binary and the Dockerfile no longer installs a separate one — see #89). Re-ran every runtime check from #89 against a freshly built image rather than assuming the bump doesn't disturb that mechanism: - claude_agent_sdk._cli_version.__cli_version__ == "2.1.220", matching the changelog's version table for 0.2.128. - SubprocessCLITransport._find_cli() still resolves to the bundled binary path inside site-packages, not a PATH lookup. - `which claude`, node, npm, git, gh all behave identically to pre-bump. - All three detect_auth() branches (no creds -> RuntimeError, OAuth token, API key) behave identically to pre-bump. Verification: - `uv run --locked pytest -q` -> 243 passed, unchanged - `uv run --locked ruff check orchestrator config tests` -> clean - `uv run --locked mypy` -> clean - Only claude-agent-sdk itself moved in uv.lock; no transitive dependency cascade.
|
Claude encountered an error after 0s —— View job I'll analyze this and get back to you. |
|
Claude finished @mashkovd's task in 20s —— View job Reviewing PR #93
Verdict: trivial dependency bump — approved. Diff is confined to
|
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.
What
Bumps
claude-agent-sdkfrom0.2.110to0.2.128— the current latest.Deliberate, isolated bump per issue #44's own convention ("bump deliberately,
in an explicit commit").
Why now
This is the first bump attempted with any real confidence, because it's the
first time there's been something to test it against: #86 gave us CI, #88
gave us a lockfile, #89 established exactly how the bundled-CLI mechanism
works, #90/#91 gave us lint/type gates. Before this series, a harness bump
was an unverifiable leap of faith.
Breaking-change review
Read the SDK's changelog for every version between
0.2.111and0.2.128,not just the target's entry. Nothing documented touches this codebase:
ResultMessage.model_usagetype changed fromdict[str, Any]todict[str, ModelUsage]. Grepped formodel_usageanywhere in
orchestrator/config: zero hits.--resume/--session-idflag format changed. Grepped forresume/session_id: zero hits.python:3.12-slimon Linux exclusively.Bundled CLI moves too — re-verified, not assumed
The bump takes the bundled CLI from
2.1.191to2.1.220as a side effect(
claude-agent-sdkships its own CLI binary; see #89 for why the Dockerfileno longer installs a separate one). Rather than assume the bundled-CLI
mechanism established in #89 still holds, re-ran the exact same checks
against a freshly built image:
node/npm/git/ghall present and unaffected. All threedetect_auth()branches (no creds →
RuntimeError, OAuth token, API key) behave identicallyto pre-bump.
Verification
uv run --locked pytest -q→ 243 passed, unchangeduv run --locked ruff check orchestrator config tests→ cleanuv run --locked mypy→ cleanclaude-agent-sdkitself moved inuv.lock— no transitivedependency cascade