Skip to content

[Snyk] Security upgrade python from 3.14.0rc2-alpine3.22 to 3.14.0-alpine3.22 #10

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

[Snyk] Security upgrade python from 3.14.0rc2-alpine3.22 to 3.14.0-alpine3.22 #10

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
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM python:3.14.0rc2-alpine3.22
FROM python:3.14.0-alpine3.22
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.

medium

For improved security and build reproducibility, it's a best practice to pin the base image to its immutable digest (SHA256) instead of a mutable tag. This protects against tag mutability, where the python:3.14.0-alpine3.22 tag could be updated to point to a different image digest.

You can find the digest for the image (for example, by running docker pull python:3.14.0-alpine3.22 and then docker inspect python:3.14.0-alpine3.22) and update the FROM instruction like this:

FROM python:3.14.0-alpine3.22@sha256:<the-sha256-digest-of-the-image>

This ensures that you are always using the exact same base image for your builds.


RUN mkdir /data && \
mkdir /igel
Expand Down
Loading