fix: make sure string responses use utf8 #2100
MiniDiggerAnnotations
5 warnings
|
build
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Legacy key/value format with whitespace separator should not be used:
chart/dockerfiles/frontend/Dockerfile#L5
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/
|
|
Legacy key/value format with whitespace separator should not be used:
chart/dockerfiles/frontend/Dockerfile#L6
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/
|
|
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes:
chart/dockerfiles/backend/Dockerfile#L7
WorkdirRelativePath: Relative workdir "hangar" can have unexpected results if the base image changes
More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/
|
|
Legacy key/value format with whitespace separator should not be used:
chart/dockerfiles/backend/Dockerfile#L9
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/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
HangarMC~Hangar~SNWZK2.dockerbuild
|
35.2 KB |
|
|
HangarMC~Hangar~WW043B.dockerbuild
|
33.1 KB |
|