chore(deps): update dependency python to 3.15

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
python	uses-with	minor	3.14 → 3.15

---

Release Notes

actions/python-versions (python)

v3.15.0: 3.15.0

Compare Source

Python 3.15.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

Looks good, straightforward CI config bump.

What was reviewed: the two-file diff bumping actions/setup-python's python-version from "3.14" to "3.15" in the docs-publish and lint jobs; confirmed both files change consistently with no other logic edits. Checked the tox.ini note "py315 commented out - requires C++ build tools for librt (mypy dependency)" — that applies to local Windows tox environments building Python from pythoncore installers, not to this CI job's use of actions/setup-python, which fetches a prebuilt Python 3.15 binary on ubuntu-latest, so it doesn't block this change.

Extended reasoning...

The diff is a two-line renovate-bot version bump (3.14 -> 3.15) applied identically to the python-version field in two GitHub Actions workflow files, with no other code or logic changes; it touches no security-sensitive surface. I checked a candidate concern that the repo's tox.ini marks py315 as unsupported locally due to missing C++ build tools for a mypy dependency, but that note is scoped to a local Windows tox setup building Python from installer binaries, whereas the CI lint job uses actions/setup-python to install a prebuilt Python 3.15 on ubuntu-latest, so the local build caveat doesn't apply here. The change is mechanical, self-contained, and low risk (CI will simply fail loudly if the 3.15 toolchain isn't actually ready), so no human review is strictly necessary.