Skip to content

chore(deps): Bump node from 21-alpine to 22-alpine (#299) #751

chore(deps): Bump node from 21-alpine to 22-alpine (#299)

chore(deps): Bump node from 21-alpine to 22-alpine (#299) #751

Re-run triggered August 20, 2024 09:04
Status Success
Total duration 1m 30s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
11s
Lint / Broken Markdown links
Lint  /  Super Linter
1m 36s
Lint / Super Linter
Build & Test  /  Build Node.js
1m 18s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
47s
Build & Test / Build Docker image
Release  /  Release Docker image
Release / Release Docker image
Fit to window
Zoom out
Zoom in

Annotations

6 warnings and 1 notice
Legacy key/value format with whitespace separator should not be used: Dockerfile#L54
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#L55
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#L50
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#L51
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: [Integration tests] › did/did-deactivate.spec.ts#L1
[Integration tests] › did/did-deactivate.spec.ts took 19.6s
Slow Test: [Integration tests] › resource/resource-create.spec.ts#L1
[Integration tests] › resource/resource-create.spec.ts took 17.7s
🎭 Playwright Run Summary
18 passed (57.2s)