[Snyk] Security upgrade python from 3.10.4 to 3.14.3#432
Open
nicholas-lockhart wants to merge 1 commit intomasterfrom
Open
[Snyk] Security upgrade python from 3.10.4 to 3.14.3#432nicholas-lockhart wants to merge 1 commit intomasterfrom
nicholas-lockhart wants to merge 1 commit intomasterfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-DEBIAN11-FREETYPE-9402510 - https://snyk.io/vuln/SNYK-DEBIAN11-FREETYPE-9402510 - https://snyk.io/vuln/SNYK-DEBIAN11-FREETYPE-9402510 - https://snyk.io/vuln/SNYK-DEBIAN11-GLIBC-5927133 - https://snyk.io/vuln/SNYK-DEBIAN11-GLIBC-5927133
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| @@ -1,4 +1,4 @@ | |||
| FROM python:3.10.4 | |||
| FROM python:3.14.3 | |||
There was a problem hiding this comment.
Major Python version jump skips untested Python 3.14
High Severity
The upgrade from python:3.10.4 to python:3.14.3 jumps 4 minor versions to a Python version that is not included in the project's official classifiers in pyproject.toml. The classifiers list Python 3.9 through 3.13 but explicitly omit Python 3.14, indicating this version has not been tested by the maintainers. This significant version jump could introduce runtime compatibility issues from deprecated API removals or behavior changes between Python 3.10 and 3.14.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):
DockerfileWe recommend upgrading to
python:3.14.3, as this image has only 219 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.Vulnerabilities that will be fixed with an upgrade:
SNYK-DEBIAN11-FREETYPE-9402510
SNYK-DEBIAN11-FREETYPE-9402510
SNYK-DEBIAN11-FREETYPE-9402510
SNYK-DEBIAN11-GLIBC-5927133
SNYK-DEBIAN11-GLIBC-5927133
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Out-of-bounds Write
Note
Medium Risk
Updating the Docker base image can introduce runtime and dependency compatibility issues despite being a straightforward, security-motivated change.
Overview
Updates the
Dockerfilebase image frompython:3.10.4topython:3.14.3to pick up upstream security fixes in the container OS/Python distribution.Written by Cursor Bugbot for commit 5e9e908. This will update automatically on new commits. Configure here.