Update python Docker tag

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
python		minor	3.10 -> 3.14
python (source)	requires-python	minor	>=3.10,<3.13 -> >=3.14,<3.15
python	stage	minor	3.11.7-slim -> 3.14.0-slim

---

Release Notes

python/cpython (python)

v3.14.0

Compare Source

v3.13.9

Compare Source

v3.13.8

Compare Source

v3.13.7

Compare Source

v3.13.6

Compare Source

v3.13.5

Compare Source

v3.13.4

Compare Source

v3.13.3

Compare Source

v3.13.2

Compare Source

v3.13.1

Compare Source

v3.13.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package python
Using CPython 3.14.0 interpreter at: /opt/containerbase/tools/python/3.14.0/bin/python3.14
warning: Resolving despite existing lockfile due to fork markers being disjoint with `requires-python`: `python_full_version >= '3.10' and python_full_version < '3.13'` vs `python_full_version == '3.14.*'`
   Updating https://github.com/danielgafni/griffe-pydantic.git (feat/configurable-bases)
    Updated https://github.com/danielgafni/griffe-pydantic.git (8bc318cafa780bc242b4f74d7613f08f0498d7fb)
  × No solution found when resolving dependencies:
  ╰─▶ Because only the following versions of ray[client] are available:
          ray[client]==0.1.1
          ray[client]==0.1.2
          ray[client]==0.2.0
          ray[client]==0.2.1
          ray[client]==0.2.2
          ray[client]==0.3.0
          ray[client]==0.3.1
          ray[client]==0.4.0
          ray[client]==0.5.0
          ray[client]==0.5.2
          ray[client]==0.5.3
          ray[client]==0.6.0
          ray[client]==0.6.1
          ray[client]==0.6.2
          ray[client]==0.6.3
          ray[client]==0.6.4
          ray[client]==0.6.5
          ray[client]==0.6.6
          ray[client]==0.7.0
          ray[client]==0.7.1
          ray[client]==0.7.2
          ray[client]==0.7.3
          ray[client]==0.7.4
          ray[client]==0.7.5
          ray[client]==0.7.6
          ray[client]==0.7.7
          ray[client]==0.8.0
          ray[client]==0.8.1
          ray[client]==0.8.2
          ray[client]==0.8.3
          ray[client]==0.8.4
          ray[client]==0.8.5
          ray[client]==0.8.6
          ray[client]==0.8.7
          ray[client]==1.0.0
          ray[client]==1.0.1
          ray[client]==1.0.1.post1
          ray[client]==1.1.0
          ray[client]==1.2.0
          ray[client]==1.3.0
          ray[client]==1.4.0
          ray[client]==1.4.1
          ray[client]==1.5.0
          ray[client]==1.5.1
          ray[client]==1.5.2
          ray[client]==1.6.0
          ray[client]==1.7.0
          ray[client]==1.7.1
          ray[client]==1.8.0
          ray[client]==1.9.0
          ray[client]==1.9.1
          ray[client]==1.9.2
          ray[client]==1.10.0
          ray[client]==1.11.0
          ray[client]==1.11.1
          ray[client]==1.12.0
          ray[client]==1.12.1
          ray[client]==1.13.0
          ray[client]==2.0.0
          ray[client]==2.0.1
          ray[client]==2.1.0
          ray[client]==2.2.0
          ray[client]==2.3.0
          ray[client]==2.3.1
          ray[client]==2.4.0
          ray[client]==2.5.0
          ray[client]==2.5.1
          ray[client]==2.6.0
          ray[client]==2.6.1
          ray[client]==2.6.2
          ray[client]==2.6.3
          ray[client]==2.7.0
          ray[client]==2.7.1
          ray[client]==2.7.2
          ray[client]==2.8.0
          ray[client]==2.8.1
          ray[client]==2.9.0
          ray[client]==2.9.1
          ray[client]==2.9.2
          ray[client]==2.9.3
          ray[client]==2.10.0
          ray[client]==2.11.0
          ray[client]==2.12.0
          ray[client]==2.20.0
          ray[client]==2.21.0
          ray[client]==2.22.0
          ray[client]==2.23.0
          ray[client]==2.24.0
          ray[client]==2.30.0
          ray[client]==2.31.0
          ray[client]==2.32.0
          ray[client]==2.33.0
          ray[client]==2.34.0
          ray[client]==2.35.0
          ray[client]==2.36.0
          ray[client]==2.36.1
          ray[client]==2.37.0
          ray[client]==2.38.0
          ray[client]==2.39.0
          ray[client]==2.40.0
          ray[client]==2.41.0
          ray[client]==2.42.0
          ray[client]==2.42.1
          ray[client]==2.43.0
          ray[client]==2.44.0
          ray[client]==2.44.1
          ray[client]==2.45.0
          ray[client]==2.46.0
          ray[client]==2.47.0
          ray[client]==2.47.1
          ray[client]==2.48.0
          ray[client]==2.49.0
          ray[client]==2.49.1
          ray[client]==2.49.2
          ray[client]==2.50.0
          ray[client]==2.50.1
      and ray[client]<=1.7.0 has no wheels with a matching Python version tag
      (e.g., `cp314`), we can conclude that ray[client]<=1.7.0 cannot be used.
      And because ray[client]==1.7.1 was yanked (reason:
      https://github.com/ray-project/ray/issues/19813) and ray[client]>=1.8.0
      has no wheels with a matching Python version tag (e.g., `cp314`), we can
      conclude that ray[client]>=1.8.0 cannot be used.
      And because dagster-ray[executor] depends on ray[client] and your
      project requires dagster-ray[executor], we can conclude that your
      project's requirements are unsatisfiable.

      hint: Pre-releases are available for `ray` in the requested range (e.g.,
      2.32.0rc0), but pre-releases weren't enabled (try: `--prerelease=allow`)

      hint: Wheels are available for `ray` (v1.7.0) with the following Python
      ABI tags: `cp36m`, `cp37m`, `cp38`, `cp39`