gpu-container v0.1.4 — beta

Patch release — cosmetic + pipeline hardening, no behavior change to the planner/profiler.

Fixed

• npm provenance "source" link now resolves to the launcher's npm/ subdirectory (repository.directory: "npm"). The 0.1.3 attestation was already valid (npm audit signatures passes); this just points the provenance source link at the real package folder.

Changed

• Release pipeline now verifies the launcher's pinned binary version/tag (npm/bin/gpu-container.js) match the release tag before publishing — closes a gap where bumping the package version alone could ship a launcher that downloads the previous release's binaries.

Channels: PyPI · npm (provenance) · Docker/ghcr · GitHub-Release binaries (linux-x64, darwin-arm64, win-x64).

gpu-container v0.1.3 — beta

Beta — first release on the fixed pipeline. Same code as 0.1.1, with the first-class npm package README (logo, badges, 8-language translations).

Install

• PyPI: pip install "gpu-container[host]"
• npx: npx gpu-container --help
• Docker: docker pull ghcr.io/mcp-tool-shop-org/gpu-container:0.1.3

v1.0.0 (stable) follows after the dogfood pass.

gpu-container v0.1.2 — beta

⚠ Superseded by v0.1.3.

Published PyPI 0.1.2 + Docker 0.1.2, but the binaries + npm launcher were blocked by a release-pipeline bug (the Docker .dockerbuild artifact reliably failed to download in release-binaries). Fixed in v0.1.3 — use v0.1.3.

gpu-container v0.1.1 — beta

⚠ Superseded by v0.1.3 (same code; v0.1.3 adds the first-class npm README). Complete 4-channel release; use v0.1.3.

gpu-container v0.1.0 — beta

⚠ Superseded by v0.1.1. Use v0.1.1.

This initial beta published to PyPI + Docker only. The standalone PyInstaller binaries and the npm launcher were correctly gated out by the binary smoke test (a relative-import crash in the frozen entry); they ship in v0.1.1. PyPI gpu-container==0.1.0 (pip) and ghcr.io/mcp-tool-shop-org/gpu-container:0.1.0 (Docker) remain valid.