feat: support Python 3.15 (#781)

* build: support Python 3.15

Raise the msgspec cap to <0.23 (0.22 is the first release with cp315
wheels), refresh the uv.lock pins that had no cp315 wheels, and add 3.15
to the CI matrices, classifiers, and installation docs.

* no-mistakes(document): Drop stale Python version range from unit test README

Author: jhamon

.github/workflows/on-push.yml

@@ -113,7 +113,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6.0.2
 
@@ -175,7 +175,7 @@ jobs:
   # declared dependencies, and touch every lazy export.
   # ---------------------------------------------------------------------------
   wheel-install-verify:
-    name: Wheel-only install verify (declared deps, py3.10-3.14)
+    name: Wheel-only install verify (declared deps, py3.10-3.15)
     runs-on: ubuntu-latest
     timeout-minutes: 25
     steps:
@@ -232,7 +232,7 @@ jobs:
           import pinecone._grpc
           print(f"OK {sys.version_info[:2]}: {len(names)} lazy exports, _grpc loaded")
           PY
-          for v in 3.10 3.11 3.12 3.13 3.14; do
+          for v in 3.10 3.11 3.12 3.13 3.14 3.15; do
             echo "::group::py${v}"
             uv python install "${v}"
             uv venv -p "${v}" "${RUNNER_TEMP}/venv-${v}"

.github/workflows/release-readiness.yml

@@ -367,10 +367,10 @@ jobs:
 
   # ---------------------------------------------------------------------------
   # Multi-Python install verify: exercises the abi3 promise on every supported
-  # Python version (3.10–3.14) using the dev wheel resolved above, which is
+  # Python version (3.10–3.15) using the dev wheel resolved above, which is
   # always built from main regardless of what ref this workflow runs against
   # (#431) — read this job's result as "main's latest published wheel loads
-  # its Rust extension and resolves its declared deps on py3.10-3.14", not as
+  # its Rust extension and resolves its declared deps on py3.10-3.15", not as
   # signal about any other ref. The published wheel is cp310-abi3, so it must
   # install and load the Rust extension on each Python we claim to support.
   # ---------------------------------------------------------------------------
@@ -385,7 +385,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]
     env:
       GCP_REGION: ${{ vars.GCP_REGION }}
       GCP_PROJECT_ID: ${{ vars.GCP_PROJECT_ID }}

docs/getting-started/installation.md

@@ -2,7 +2,7 @@
 
 ## Prerequisites
 
-- Python 3.10 or newer. Python 3.10 through 3.14 are tested and published for.
+- Python 3.10 or newer. Python 3.10 through 3.15 are tested and published for.
 - A [Pinecone account](https://app.pinecone.io) and an API key. See
   [Authentication](authentication.md) for where the SDK looks for it.
 

pyproject.toml

@@ -25,6 +25,7 @@ classifiers = [
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",
     "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: 3.15",
     "Topic :: Database",
     "Topic :: Software Development",
     "Topic :: Software Development :: Libraries",
@@ -36,7 +37,9 @@ dependencies = [
     # drops symbols (e.g. httpx.BaseTransport) the SDK relies on. Without this
     # cap, `pip install --pre pinecone` resolves httpx to a broken pre-release.
     "httpx[http2]>=0.27,<1.0",
-    "msgspec>=0.19,<0.22",
+    # 0.22 is the first msgspec release with cp315 wheels; a lower cap makes
+    # `pip install pinecone` on Python 3.15 build msgspec from source.
+    "msgspec>=0.19,<0.23",
     "orjson>=3.11,<4",
     # Imported at module scope by pinecone/async_client/assistants.py for async
     # file IO. httpx happens to require it too, but every module the package

tests/unit/README.md

@@ -20,10 +20,9 @@ under `[tool.coverage.run]` / `[tool.coverage.report]`, so a bare `--cov`
 
 ## CI behavior
 
-- Every matrix leg (`py3.10`–`py3.14`) runs with `--cov`, but only the
-  `py3.12` leg posts a markdown table to the GitHub Actions job summary —
-  posting it five times over would just be duplicate noise on the PR
-  checks tab.
+- Every matrix leg runs with `--cov`, but only the `py3.12` leg posts a
+  markdown table to the GitHub Actions job summary — posting it once per
+  leg would just be duplicate noise on the PR checks tab.
 - There is **no failure threshold**. A floor set before there's real data
   on where coverage naturally sits gets gamed with tests that execute
   lines without asserting anything — worse than no signal. Revisit this