Python SDK version 1.0.3 only has wheels for macos

[TaoChenOSU]

Upon upgrading my dev env, pip reported the following error:

On Pypi, it shows only the following:

Temporary work around is to pin our dependency to 1.0.2. Please publish the wheels for all platforms in future releases.

[github-actions]

Investigation Findings: Confirmed Bug

Thanks for the report. I investigated the Python SDK publish pipeline and confirmed this is a bug in the wheel-build script.

What I looked at

• .github/workflows/publish.yml — the publish-python job runs node scripts/build-wheels.mjs --output-dir dist (no --platform flag) and publishes whatever lands in python/dist/
• python/scripts/build-wheels.mjs — the script that downloads CLI binaries from the npm registry and builds per-platform wheels for 6 targets: linux-x64, linux-arm64, darwin-x64, darwin-arm64, win32-x64, win32-arm64

Root cause

The main() loop in build-wheels.mjs (lines 352–361) has overly permissive error handling:

for (const p of platforms) {
    try {
        const wheel = await buildWheel(p, pkgVersion, cliVersion, outputDir, licensePath);
        wheels.push(wheel);
    } catch (e) {
        console.error(`Error building wheel for ${p}:`, e.message);
        if (platform) {   // ← only exits if a single --platform was specified
            process.exit(1);
        }
        // ← when building ALL platforms, the error is swallowed and the loop continues
    }
}

When running without --platform (the publish workflow path), any per-platform failure is silently swallowed and the script exits with code 0. The publish job then uploads whatever partial set of wheels was successfully built to PyPI.

For the v1.0.3 release, the linux and Windows CLI platform binaries appear to have been unavailable on the npm registry (or failed to download for another reason) when the release job ran. Only the darwin-x64 and darwin-arm64 downloads succeeded, so only macOS wheels were published — with no CI failure to catch the gap.

Fix needed

The main() loop should track failures and exit with a non-zero code if any platform fails to build, so the publish job fails visibly rather than silently publishing an incomplete wheel set. A minimal fix:

let failed = 0;
for (const p of platforms) {
    try {
        const wheel = await buildWheel(...);
        wheels.push(wheel);
    } catch (e) {
        console.error(`Error building wheel for ${p}:`, e.message);
        failed++;
    }
}
if (failed > 0) {
    console.error(`\n${failed} platform(s) failed to build.`);
    process.exit(1);
}

The 1.0.3 release will also need to be re-published with a complete set of wheels (or a patch release 1.0.4 that includes all platform wheels).

Generated by Bug Handler for issue #1751 · sonnet46 899.6K · ◷