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.

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

fix: update curl version #64

Merged
merged 1 commit into from
Nov 11, 2024
Merged

fix: update curl version #64

Show file tree
Hide file tree
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
Expand Up @@ -4,7 +4,7 @@

# Gems have to be ARG and ENV because they are used as reference in the Gemfile
ARG RUBYGEM_PUPPET
ENV RUBYGEM_PUPPET ${RUBYGEM_PUPPET:-8.8.1}

Check warning on line 7 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build x86 CI container (7, docker.io/ruby:2.7.8-alpine3.16, 7.34.0, 4.10.0, 9.2.0, 3.2.0, 3.1.0, ...

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/

Check warning on line 7 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build ARM CI container (7, docker.io/ruby:2.7.8-alpine3.16, 7.34.0, 4.10.0, 9.2.0, 3.2.0, 3.1.0, ...

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/

Check warning on line 7 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build x86 CI container (8, docker.io/ruby:3.2.5-alpine3.20, 8.10.0, 4.10.0, 9.2.0, 3.2.0, 3.1.0, ...

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/

Check warning on line 7 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build ARM CI container (8, docker.io/ruby:3.2.5-alpine3.20, 8.10.0, 4.10.0, 9.2.0, 3.2.0, 3.1.0, ...

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/

ARG RUBYGEM_FACTER
ENV RUBYGEM_FACTER=${RUBYGEM_FACTER:-4.8.0}
Expand Down Expand Up @@ -76,7 +76,7 @@
ARG APK_JQ=1.7.1-r0
ARG APK_YAMLLINT=1.35.1-r1
ARG APK_GIT=2.45.2-r0
ARG APK_CURL=8.10.1-r0
ARG APK_CURL=8.11.0-r1

RUN apk update \
&& apk upgrade \
Expand Down
2 changes: 1 addition & 1 deletion build_versions.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@
"apk_jq": "1.7.1-r0",
"apk_yamllint": "1.35.1-r1",
"apk_git": "2.45.2-r0",
"apk_curl": "8.10.1-r0"
"apk_curl": "8.11.0-r1"
}
]
}
Loading