Skip to content

Commit

Permalink
Merge pull request #958 from traPtitech/dependabot/docker/non-majors-…
Browse files Browse the repository at this point in the history 
…201241d026

build(deps): bump golang from 1.22-alpine to 1.23-alpine in the non-majors group
  • Loading branch information
@pirosiki197
pirosiki197 authored Sep 2, 2024
2 parents 03d8696 + 7575497 commit 06b1b77
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Dockerfile
View file
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM --platform=$BUILDPLATFORM golang:1.22-alpine AS builder
FROM --platform=$BUILDPLATFORM golang:1.23-alpine AS builder

WORKDIR /work
ENV CGO_ENABLED 0

Check warning on line 4 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build Base Image

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 4 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build Component Images (ns-builder)

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 4 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build Component Images (ns-controller)

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 4 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build Component Images (ns-gateway)

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 4 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build Component Images (ns-gitea-integration)

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 4 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build Component Images (ns-migrate)

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 4 in Dockerfile

View workflow job for this annotation

GitHub Actions / Build Component Images (ns-ssgen)

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/
Expand Down

0 comments on commit 06b1b77

Please sign in to comment.