Skip to content

[Snyk] Security upgrade python from 3.14.0a1-slim to 3.14.0-slim #6

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

[Snyk] Security upgrade python from 3.14.0a1-slim to 3.14.0-slim #6

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 Dockerfile.frontend
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Use an official Python runtime as a parent image
FROM python:3.14.0a1-slim as frontend
FROM python:3.14.0-slim as frontend
Copy link

@gemini-code-assist gemini-code-assist bot Oct 11, 2025

Choose a reason for hiding this comment

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

high

While upgrading to a stable Python version is a good practice, using Python 3.14 here raises a couple of significant concerns:

  1. Potential for Build Failures: Using a very recent Python version like 3.14 can be risky as many dependencies may not have pre-compiled wheels available for it. For example, pyarrow, a dependency of streamlit, does not have wheels for Python 3.14 in the locked version. This would force poetry to build it from source, but this Dockerfile lacks the necessary build toolchain (e.g., C++ compiler, CMake), which would likely cause the build to fail.

  2. Inconsistent Python Versions: This change sets the frontend to use Python 3.14, while the backend (Dockerfile) uses Python 3.11. Managing different Python versions across services increases maintenance complexity and can lead to subtle inconsistencies.

Considering these points, it would be more reliable and maintainable to use a more established Python version for which dependencies are readily available, such as Python 3.11, to align with the backend.


# Set environment variables
ENV PYTHONDONTWRITEBYTECODE 1
Expand Down