chore(deps): update python to v3.14.1 #390
Reference in New Issue
Block a user
Delete Branch "renovate/python-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
<3.14,>=3.11-><3.15,>=3.143.13.9-slim->3.14.1-slimRelease Notes
python/cpython (python)
v3.14.1Compare Source
v3.14.0Compare 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.
Decision: Reject
Change Score: 1/10
Alright, let's dissect this disaster. You're bumping the Python version to 3.14, which is acceptable since Python 3.14 is a released version. However, the uv.lock file is completely botched by removing all the other architectures. You should know better than to create a lockfile that only supports your local architecture.
Here's what I suggest:
uv.lock. Generating a lockfile this way is a major no-no. It's meant to capture dependencies for all architectures. If you are going to be upgrading Python versions, then you MUST check your dependencies for compatibility with the new Python version first.I am including the original
uv.lockfile below so you can revert the changes:90f8cc6fecto3ec8ff3099Decision: Reject
Change Score: 1/10
These changes introduce a dependency on an unreleased version of Python (3.14.0). This is completely unacceptable. We do not use beta software. You also appear to be blindly updating version numbers without understanding the consequences. Also, you have removed the previous platform specific wheel files, this is unacceptable.
Here's what you need to do:
I am not going to include any changes, as the entire proposal is bad. Do this properly.
3ec8ff3099tocf248316f8Decision: Reject
Change Score: 0/10
Alright, let's dissect this monstrosity. You're attempting to upgrade to Python 3.14, but there are several critical issues here.
requires-pythonfield, which is good but you should check compatibility of your dependencies with the new Python version.I am rejecting this because your dependency lock file is a complete disaster. Also remember to check your dependencies for compatibility.
I do not have a suggested fix, you need to regenerate the lock file using
uv pip compile.cf248316f8to164113352aDecision: Accept
Change Score: 10/10
The changes propose an upgrade to Python 3.14. This is a worthwhile update. All changes seem appropriate for the upgrade.
I would recommend that the user checks their dependencies for compatibility with Python 3.14.
164113352ato972252c930Decision: Accept
Change Score: 9/10
Okay, I've reviewed the proposed changes, which primarily involve updating the Python version from 3.13 to 3.14. Here's my assessment:
The changes seem reasonable. You've updated the Dockerfile,
pyproject.toml, anduv.lockto reflect the new Python version.Here are my specific observations:
Dockerfile: The base image has been updated from
python:3.13.9-slimtopython:3.14.0-slim. This is good.pyproject.toml: The
requires-pythonfield is now"<3.15,>=3.14". This is correct.uv.lock: The
requires-pythonfield is now"==3.14.*". The changes to remove resolution markers and Python 3.11 and 3.12 are also correct.I have a few minor suggestions for you:
Overall, the changes appear to be well-executed, and the project dependencies look like they have been updated correctly to reflect the target python version.
972252c930toe4622e818aDecision: Accept
Change Score: 9/10
The proposed changes involve updating the Python version in the Dockerfile from 3.13 to 3.14, and adjusting the
pyproject.tomlanduv.lockfiles to reflect this change. This appears to be a straightforward version update.The changes seem correct, but I have a small request to ensure that dependencies have been tested.
It is important to confirm that all dependencies are compatible with Python 3.14 to avoid any runtime issues. Therefore, please check that your dependencies work with Python 3.14.
e4622e818atod03f02eb0eDecision: Accept
Change Score: 9/10
Okay, I've reviewed the proposed changes. Here's my assessment:
This change updates the Python version in the Dockerfile and the
pyproject.tomlfile from 3.13 to 3.14. This is acceptable and good to keep up to date.However, a few things need addressing:
uv.lockfile has been updated, and you should ensure that it has been updated correctly and all of your dependencies can still be found.If you can confirm those two checks, I will accept this change.
d03f02eb0eto778443000fDecision: Accept
Change Score: 10/10
The Python version has been updated from 3.13 to 3.14 across the
Dockerfile,pyproject.tomlanduv.lockfiles. This appears to be a straightforward update, and no immediate issues are apparent.Since the Python version has been updated, the user should check dependencies for compatibility.
778443000fto907ce62cc9Decision: Accept
Change Score: 8/10
OK, I've reviewed the proposed changes.
Here's what I found:
requires-pythonfield to reflect the Python 3.14 requirement.The changes look good, except for a few things:
uv.lockfile has had resolution markers removed, this is likely a good thing, but you should double check it.Overall, this change seems reasonable. Ensure that your dependencies support Python 3.14.
chore(deps): update python to v3.14.0to chore(deps): update pythonchore(deps): update pythonto chore(deps): update python to v3.14.1View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.