Bug: claude-agent-sdk 0.2.144 is a partial publish

[bai-uipath]

Bug: claude-agent-sdk 0.2.144 is the latest version on PyPI but was never actually released.

The releases page still shows 0.2.143 as latest. Did a publish job die partway through?

[tonydzi]

Confirmed, and the shape is narrower than a dead job: exactly one file is missing, and it happens to be the one that changes behaviour rather than just availability.

What is actually missing

0.2.144 published 4 wheels. 0.2.140 through 0.2.143 each published 5. The gap is win_amd64:

0.2.140  macosx_arm64  macosx_x86_64  manylinux_aarch64  manylinux_x86_64  win_amd64
0.2.141  ... same 5
0.2.142  ... same 5
0.2.143  ... same 5
0.2.144  macosx_arm64  macosx_x86_64  manylinux_aarch64  manylinux_x86_64     --

The upload order is visible in the timestamps, and it is stable across releases: sdist first, win_amd64 last (0.2.143: sdist 20:47:43Z ... win_amd64 20:48:19Z). 0.2.144 ran sdist 20:12:01Z through manylinux_x86_64 20:12:25Z and then stopped. There is also no v0.2.144 tag and no GitHub release. So the job died after the fourth wheel and before both the last upload and the tag/release step.

Why this is not just "one platform cannot install"

pip on Windows will not fail. It falls back to the sdist and the install succeeds. But the sdist carries no CLI: the wheels are 92-104 MB because scripts/download_cli.py fetches and bundles the binary during the wheel build, while the sdist is 344,707 bytes and its build-backend is plain hatchling.build with no build hook, so nothing fetches anything on an sdist install. Unpacked, it has no file over 1 MB; src/claude_agent_sdk/_bundled/ ships but contains only a 74-byte .gitignore.

At runtime _find_bundled_cli() then returns None (subprocess_cli.py:333) and resolution falls through to shutil.which("claude") at :256. Two outcomes:

• Windows box with no system CLI: CLINotFoundError. Loud, and the reporter would have filed that instead.
• Windows box with Claude Code already on PATH, which covers most CI runners and most dev machines: it silently runs against that CLI, at whatever version is installed.

Nothing catches the second case. __cli_version__ = "2.1.239" in src/claude_agent_sdk/_cli_version.py is read only by scripts/build_wheel.py and scripts/update_cli_version.py, both build-time; grepping __cli_version__ across src/ returns the assignment and nothing else. There is no runtime comparison between the pin and the binary that actually got resolved.

Net effect: a Windows job that pins claude-agent-sdk==0.2.144 installs green, reports 0.2.144, and runs an unpinned CLI. Yanking 0.2.144 closes that window immediately by sending Windows resolution back to 0.2.143's wheel, which seems worth doing ahead of the re-publish rather than after it.