Update dependency ol to v10.3.1 #17092
ci.yml
on: pull_request
typescript
1m 2s
vitest
1m 10s
minitest
3m 1s
docker-build
4m 32s
Build doc site
2m 19s
update-release-draft
0s
Annotations
17 warnings
typescript
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
vitest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build doc site
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
minitest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
minitest
No artifacts found for the following workspaces: ci,cron
|
minitest
main is missing coverage/coverage.xml. See documentation on how to add this
|
docker-build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Default value for global ARG results in an empty or invalid base image name:
Dockerfile#L47
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name
More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L38
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_ACCESS_KEY_ID")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L60
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/
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
Dockerfile#L96
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
The 'as' keyword should match the case of the 'from' keyword:
Dockerfile#L47
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L39
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:
Dockerfile#L61
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:
Dockerfile#L62
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/
|
The 'as' keyword should match the case of the 'from' keyword:
Dockerfile#L55
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L36
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 | |
---|---|---|
minitest-reports
|
25 KB |
|
neinteractiveliterature~intercode~RAUL2G.dockerbuild
|
111 KB |
|
vitest-reports
|
513 KB |
|