Skip to content

bump eslint plugins #2579

bump eslint plugins

bump eslint plugins #2579

Triggered via push September 10, 2024 10:39
Status Success
Total duration 7m 17s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
3m 8s
Lint / Broken Markdown links
Lint  /  Super Linter
6m 44s
Lint / Super Linter
Build & Test  /  Build Node.js
7m 5s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
6m 10s
Build & Test / Build Docker image
Release  /  Release Docker image
Release / Release Docker image
Fit to window
Zoom out
Zoom in

Annotations

12 warnings and 2 notices
🎭 Playwright Run Summary
1 skipped 61 passed (2.5m)
🎭 Playwright Run Summary
9 passed (2.5m)
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L144
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: docker/Dockerfile#L112
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: docker/Dockerfile#L116
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: docker/Dockerfile#L124
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: docker/Dockerfile#L106
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "EXTERNAL_DB_ENCRYPTION_KEY") 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: docker/Dockerfile#L113
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: docker/Dockerfile#L115
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: docker/Dockerfile#L120
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: docker/Dockerfile#L142
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "STRIPE_PUBLISHABLE_KEY") 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: docker/Dockerfile#L100
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/
Slow Test: [Logged In User Tests] › sequential/credential/suspension-flow.spec.ts#L1
[Logged In User Tests] › sequential/credential/suspension-flow.spec.ts took 1.5m
Slow Test: [Logged In User Tests] › sequential/credential/revocation-flow.spec.ts#L1
[Logged In User Tests] › sequential/credential/revocation-flow.spec.ts took 55.1s

Artifacts

Produced during runtime
Name Size
cheqd~studio~E21QZV.dockerbuild Expired
55.7 KB
studio-staging Expired
704 MB