Skip to content

Linting a random file to see if build runs as expected (#190) #158

Linting a random file to see if build runs as expected (#190)

Linting a random file to see if build runs as expected (#190) #158

Triggered via push November 1, 2024 18:03
Status Success
Total duration 53s
Artifacts

release.yaml

on: push
create_release  /  release
11s
create_release / release
build_container  /  build
44s
build_container / build
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
create_release / release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/create-release@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
create_release / release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/create-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
create_release / release
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/
create_release / release
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/
create_release / release
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/
build_container / build
Process "docker run" closed with code 1