Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 3, 2025

This PR contains the following updates:

Package Type Update Change
python minor 3.103.14
python (source) requires-python minor >=3.10,<3.14>=3.14,<3.15
python (source) requires-python minor >=3.10,<3.13>=3.14,<3.15

Release Notes

python/cpython (python)

v3.14.2

Compare Source

v3.14.1

Compare Source

v3.14.0

Compare Source


Configuration

📅 Schedule: 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 is behind base branch, 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
Copy link
Contributor Author

renovate bot commented Oct 3, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts 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.2 interpreter at: /opt/containerbase/tools/python/3.14.2/bin/python3
  × No solution found when resolving dependencies:
  ╰─▶ Because only the following versions of aimrocks are available:
          aimrocks<0.5.dev0
          aimrocks>=0.5.0,<=0.5.2
      and aimrocks>=0.5.0 has no wheels with a matching Python version tag
      (e.g., `cp314`), we can conclude that aimrocks>=0.5.0 cannot be used.
      And because all of:
          aim>=3.23.0,<=3.28.0
          aim==3.29.1
      depend on aimrocks>=0.5.dev0 and only the following versions of aim
      are available:
          aim<=3.23.0
          aim==3.24.0
          aim==3.25.0
          aim==3.25.1
          aim==3.26.1
          aim==3.27.0
          aim==3.28.0
          aim==3.29.0
          aim==3.29.1
          aim==4.0.0
          aim==4.0.1
          aim==4.0.2
          aim==4.0.3
      we can conclude that all of:
          aim>=3.23.0,<3.29.0
          aim>3.29.0,<4.0.0
       cannot be used.
      And because all of:
          aim==3.29.0
          aim>=4.0.0
       were yanked and your project depends on aim>=3.23.0, we can conclude
      that your project's requirements are unsatisfiable.

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

      hint: `aimrocks` was requested with a pre-release marker (e.g., all of:
          aimrocks>=0.5.dev0,<0.5.0
          aimrocks>0.5.2
      ), but pre-releases weren't enabled (try: `--prerelease=allow`)

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

      hint: Wheels are available for `aimrocks` (v0.5.2) with the following
      Python ABI tags: `cp36m`, `cp37m`, `cp38`, `cp39`, `cp310`, `cp311`,
      `cp312`

File name: uv.lock
Command failed: uv lock --upgrade-package python
Using CPython 3.14.2 interpreter at: /opt/containerbase/tools/python/3.14.2/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.14'` vs `python_full_version == '3.14.*'`
  × No solution found when resolving dependencies:
  ╰─▶ Because only the following versions of ray[serve] are available:
          ray[serve]<=2.9.0
          ray[serve]==2.9.1
          ray[serve]==2.9.2
          ray[serve]==2.9.3
          ray[serve]==2.10.0
          ray[serve]==2.11.0
          ray[serve]==2.12.0
          ray[serve]==2.20.0
          ray[serve]==2.21.0
          ray[serve]==2.22.0
          ray[serve]==2.23.0
          ray[serve]==2.24.0
          ray[serve]==2.30.0
          ray[serve]==2.31.0
          ray[serve]==2.32.0
          ray[serve]==2.33.0
          ray[serve]==2.34.0
          ray[serve]==2.35.0
          ray[serve]==2.36.0
          ray[serve]==2.36.1
          ray[serve]==2.37.0
          ray[serve]==2.38.0
          ray[serve]==2.39.0
          ray[serve]==2.40.0
          ray[serve]==2.41.0
          ray[serve]==2.42.0
          ray[serve]==2.42.1
          ray[serve]==2.43.0
          ray[serve]==2.44.0
          ray[serve]==2.44.1
          ray[serve]==2.45.0
          ray[serve]==2.46.0
          ray[serve]==2.47.0
          ray[serve]==2.47.1
          ray[serve]==2.48.0
          ray[serve]==2.49.0
          ray[serve]==2.49.1
          ray[serve]==2.49.2
          ray[serve]==2.50.0
          ray[serve]==2.50.1
          ray[serve]==2.51.0
          ray[serve]==2.51.1
          ray[serve]==2.51.2
          ray[serve]==2.52.0
          ray[serve]==2.52.1
          ray[serve]==2.53.0
      and ray[serve]>=2.9.0 has no wheels with a matching Python version tag
      (e.g., `cp314`), we can conclude that ray[serve]>=2.9.0 cannot be used.
      And because ado-core depends on ray[serve]>=2.9 and your workspace
      requires ado-core, we can conclude that your workspace'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` (v2.53.0) with the following Python
      ABI tags: `cp310`, `cp311`, `cp312`, `cp313`

@renovate renovate bot force-pushed the renovate/python-3.x branch 7 times, most recently from 6fc2928 to df38f02 Compare October 10, 2025 09:18
@renovate renovate bot force-pushed the renovate/python-3.x branch 13 times, most recently from 74feccc to b795d79 Compare October 20, 2025 08:38
@renovate renovate bot force-pushed the renovate/python-3.x branch 7 times, most recently from c3c0b51 to 5ae47d2 Compare October 23, 2025 10:19
@renovate renovate bot force-pushed the renovate/python-3.x branch 2 times, most recently from ff56ca3 to 73eca63 Compare October 30, 2025 08:49
@renovate renovate bot force-pushed the renovate/python-3.x branch 27 times, most recently from 8632d96 to 90c9130 Compare January 16, 2026 10:39
@renovate renovate bot force-pushed the renovate/python-3.x branch from 90c9130 to 168bd03 Compare January 16, 2026 11:11
@renovate renovate bot force-pushed the renovate/python-3.x branch from 168bd03 to 5e65fe5 Compare January 16, 2026 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant