Skip to content

[Snyk] Security upgrade python from 3.9.15 to 3.14.2 #425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
madisonmay wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade python from 3.9.15 to 3.14.2 #425

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion readme_docs/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM python:3.9.15
FROM python:3.14.2
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Dec 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update base image to an existing Python tag

readme_docs/Dockerfile now starts from python:3.14.2, but the official Python images currently only publish tags up to 3.13.x, so python:3.14.2 cannot be pulled. Any build of this image will fail immediately at the FROM instruction. Please pick a Python tag that actually exists (e.g., the latest 3.13.x or the previously used 3.9.x/3.10.x).

Useful? React with 👍 / 👎.

Copy link

@cursor cursor bot Dec 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Untested Python version upgrade may break build

The upgrade from Python 3.9.15 to 3.14.2 is a significant version jump (5 major versions). The project's pyproject.toml classifiers explicitly list Python 3.9-3.13 as supported versions but do NOT include Python 3.14, indicating this version hasn't been tested. While the uv.lock has resolution markers for Python 3.14, the declared supported versions suggest potential compatibility issues. Features deprecated in 3.9 may have been removed in 3.14, which could cause the uv sync --locked command or the application itself to fail.

Fix in Cursor Fix in Web


COPY --from=ghcr.io/astral-sh/uv:latest /uv /usr/local/bin/uv

Expand Down