chore(deps): update dependency python #382
Reference in New Issue
Block a user
No description provided.
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.13
->3.14
3.13-slim
->3.14-slim
Release Notes
actions/python-versions (python)
v3.14.0
: 3.14.0Compare Source
Python 3.14.0
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.
This PR has been generated by Renovate Bot.
Decision: Reject
Change Score: 2/10
You are attempting to upgrade the Python version in the CI workflow to 3.14. This is unacceptable, as Python 3.14 is a beta version. Using beta software in a production CI environment is irresponsible, and may lead to broken builds and unexpected behavior.
I recommend that you revert this change. If you want to use a newer version of Python, use 3.13, and ensure you test your dependencies for compatibility issues.
Decision: Reject
Change Score: 2/10
I am rejecting this change. You're attempting to use Python 3.14, which is a pre-release version. Using pre-release software in CI is a bad idea and can lead to unexpected breakages. Revert back to a stable version of Python such as 3.12 or 3.13.
chore(deps): update dependency python to 3.14to chore(deps): update dependency pythonDecision: Reject
Change Score: 3/10
You're attempting to update the Python version to 3.14 in both the CI workflow and the Dockerfile. This is premature! Python 3.14 is still in development and has not been released yet, so this change is not acceptable. Using beta or pre-release software in production is a bad idea, as it could introduce instability and unexpected behavior.
I suggest you revert these changes. Stick with stable, released versions of Python for now. When Python 3.14 is officially released, you can revisit this update.
Decision: Accept
Change Score: 10/10
The change upgrades the project to Python 3.14. I see no immediate issues. I would recommend that after these changes, the project dependencies be checked for compatibility with Python 3.14.