Skip to content

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

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 latest #418

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 Dec 16, 2025

Choose a reason for hiding this comment

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

Bug: Using floating latest tag breaks build reproducibility

Changing from python:3.9.15 to python:latest creates non-reproducible builds since the latest tag is mutable and can change at any time. This conflicts with the uv sync --locked command on line 8, which is designed for reproducible installs. When latest points to a new Python version (e.g., beyond 3.13), the build may fail since dependencies like msgpack-numpy==0.4.4.3 may not support it yet. Consider using a specific version tag like python:3.12 or python:3.13 instead.

Fix in Cursor Fix in Web


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

Expand Down