Skip to content
Build

ci: Use GITHUB_OUTPUT envvar instead of set-output command #801

Sign in to view logs

ci: Use GITHUB_OUTPUT envvar instead of set-output command

ci: Use GITHUB_OUTPUT envvar instead of set-output command #801

Re-run triggered January 2, 2024 13:29
@asvobodaasvoboda
#359
master
Status Success
Total duration 7m 31s
Artifacts 1

build.yml

on: pull_request
Verify
1m 43s
Verify
Dist
5m 27s
Dist
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Verify
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Dist
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2, actions/cache@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
dist Expired
84.9 MB