Continuous integration

Update dependency @rollup/plugin-node-resolve to v15.3.0 #15253

Sign in to view logs

Triggered via pull request September 24, 2024 21:58

opened #9550

renovate/rollup-plugin-node-resolve-15.x-lockfile

Status Success

Total duration 4m 33s

Artifacts 3

ci.yml

on: pull_request

update-release-draft

Annotations

12 warnings

No artifacts found for the following workspaces: ci,cron

main is missing coverage/coverage.xml. See documentation on how to add this

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/

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L87

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/

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#L37

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#L38

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/

Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L39

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SECRET_ACCESS_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

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/

Default value for global ARG results in an empty or invalid base image name: Dockerfile#L6

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/

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/

Artifacts

Produced during runtime

Name	Size
minitest-reports Expired	25 KB
neinteractiveliterature~intercode~MH7AXV.dockerbuild Expired	106 KB
vitest-reports Expired	502 KB