Skip to content

[Snyk] Security upgrade python from 3.9.15 to latest #439

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
sihrc wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade python from 3.9.15 to latest #439

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:latest
Copy link

@cursor cursor bot Mar 5, 2026

Choose a reason for hiding this comment

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

Floating latest tag breaks Docker build reproducibility

Medium Severity

Using python:latest instead of a pinned version tag (e.g. python:3.13) makes this Docker build non-reproducible and fragile. The uv sync --locked command on line 8 requires the lockfile to match the current environment — when latest advances to a new Python minor version (e.g. 3.14, 3.15), the locked dependencies may become incompatible or unavailable for that version, causing build failures. Pinned dependencies like msgpack-numpy==0.4.4.3 are especially at risk of not supporting future Python releases.

Fix in Cursor Fix in Web


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

Expand Down