Skip to content

[Snyk] Security upgrade nginx from 1.29.3-alpine to 1.29.5-alpine #150

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

[Snyk] Security upgrade nginx from 1.29.3-alpine to 1.29.5-alpine #150

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 docker/frontend/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ RUN npm install --omit=dev --omit=optional

RUN npm run build

FROM nginx:1.29.3-alpine
FROM nginx:1.29.5-alpine
Copy link

@gemini-code-assist gemini-code-assist bot Feb 7, 2026

Choose a reason for hiding this comment

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

medium

To enhance reproducibility and prevent potential supply chain attacks, it is a best practice to pin Docker images to a specific digest rather than just a tag. While nginx:1.29.5-alpine is a good upgrade, consider adding the SHA256 digest to ensure that the exact same image is always used, even if the tag were to be repointed in the future. You can find the digest on Docker Hub or by pulling the image locally and inspecting it.


WORKDIR /patch

Expand Down