Skip to content
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.

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

[Snyk] Security upgrade ruby from 3.1-alpine to 3.3.5-alpine #707

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
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 3.1/18/alpine/Dockerfile
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
FROM ruby:3.1-alpine
FROM ruby:3.3.5-alpine
LABEL maintainer "Tim Brust <github@timbrust.de>"

Check warning on line 2 in 3.1/18/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/18/alpine, 3.1-alpine-18 3.1-alpine-hydrogen, linux/amd64,linux/arm64,linux/ppc64le,l...

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

ARG REFRESHED_AT
ENV REFRESHED_AT $REFRESHED_AT

Check warning on line 5 in 3.1/18/alpine/Dockerfile

View workflow job for this annotation

GitHub Actions / buildx (3.1/18/alpine, 3.1-alpine-18 3.1-alpine-hydrogen, linux/amd64,linux/arm64,linux/ppc64le,l...

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

RUN apk -U upgrade \
&& apk add --no-cache \
Expand Down
Loading