Skip to content

[Fix] Using node 18 in Dockerfile #58

[Fix] Using node 18 in Dockerfile

[Fix] Using node 18 in Dockerfile #58

Triggered via push January 4, 2024 19:41
Status Success
Total duration 1m 22s
Artifacts

ci.yml

on: push
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
ci (ubuntu-latest, lts/*)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (ubuntu-latest, lts/*)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
ci (ubuntu-latest, lts/*)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
ci (ubuntu-latest, lts/*)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
ci (ubuntu-latest, lts/*)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/