baseten-performance-client: Add versions 0.1.15, 0.1.15.post1

[riseproject-dev]

Automatically generated by the nightly check_versions.py run.

baseten-performance-client v0.1.14 -> v0.1.15, v0.1.15.post1

Every - version: entry added to docs/packages/baseten-performance-client.yaml is built by this PR's own build-baseten-performance-client.yml run; merging publishes the wheels.

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://riseproject-dev.github.io/python-wheels/pr-preview/pr-2460/
Built to branch gh-pages at 2026-10-02 08:25 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[luhenry]

CI failure root-caused, not fixed yet: every build job fails at git apply python-wheels/patches/baseten-performance-client/0.1.15/00*.patch with "No such file or directory" — this nightly-upgrade PR only added - version: 0.1.15 to docs/packages/baseten-performance-client.yaml; it didn't create a matching patches/baseten-performance-client/0.1.15/ directory, and the workflow's patch step has no fallback when one is missing.

This package is unusually hard to nightly-bump automatically: basetenlabs/truss is a monorepo with no git tags for this sub-package (releases are plain commits), so build-baseten-performance-client.yml hardcodes BASETEN_PERFORMANCE_CLIENT_REF to the exact commit whose python_bindings/pyproject.toml reads the pinned version — and that REF also needs bumping together with the version, which the nightly bot doesn't know to do.

I confirmed PyPI has a real final 0.1.15 release (uploaded 2026-09-29, cp38-abi3 wheel tag unchanged from 0.1.14 — so the existing 0001-python_bindings-bump-abi3-floor-to-py39.patch still applies unmodified once the REF is right). What I couldn't pin down: truss's main branch HEAD currently reads python_bindings/pyproject.toml version 0.1.15rc1 (already past the final release, bumped for the next cycle), so the exact commit matching final 0.1.15 is further back in history than this session's disk budget allowed me to bisect (shallow clones only, no room for a deeper fetch).

Needs: find the truss commit whose python_bindings/pyproject.toml reads 0.1.15 (not rc), then add both BASETEN_PERFORMANCE_CLIENT_REF (in the workflow) and a copied-forward patches/baseten-performance-client/0.1.15/ directory in the same commit.