Skip to content
Deploy to staging

chore: update dependencies #105

Sign in to view logs

chore: update dependencies

chore: update dependencies #105

Triggered via pull request September 4, 2024 11:38
@NilsOveTenNilsOveTen
opened #31
chore/not/bump
Status Success
Total duration 2m 11s
Artifacts 1

deploy-staging.yaml

on: pull_request
Run tests
1m 34s
Run tests
Build query-cache when pull request is created  /  Build, test, publish staging
1m 11s
Build query-cache when pull request is created / Build, test, publish staging
Deploy to staging environment with reusable workflow  /  Deploy to staging environment
17s
Deploy to staging environment with reusable workflow / Deploy to staging environment
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L1
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#L3
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#L4
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#L13
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#L14
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#L20
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/
Run tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-go@v2, codecov/codecov-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
Informasjonsforvaltning~catalog-history-service~QYR3OU.dockerbuild Expired
24.9 KB