Skip to content
Test

chore: bump node-forge from 1.3.1 to 1.3.2 #189

Sign in to view logs

chore: bump node-forge from 1.3.1 to 1.3.2

chore: bump node-forge from 1.3.1 to 1.3.2 #189

Triggered via pull request January 2, 2026 12:46
@addetzaddetz
synchronize #71
dependabot/npm_and_yarn/node-forge-1.3.2
Status Success
Total duration 9m 45s
Artifacts 2

test.yaml

on: pull_request
Docker Dev image
9m 40s
Docker Dev image
Docker Dev w/Proxy image
9m 17s
Docker Dev w/Proxy image
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.Caddy#L22
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L18
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size Digest
spectrocloud~hello-universe~G9A347.dockerbuild
97.8 KB
sha256:fe3658586bc4e0aaeadf387ba048b134a0c9d630b4213a5aabe4850034618ebc
spectrocloud~hello-universe~KWLCDL.dockerbuild
121 KB
sha256:8d20c0160f548470bb4220063d917a042aa593f20242cb3c77fb2a9de7f823ef