Skip to content
CI

fix: correctly check whether CI is running on release or not #33

Sign in to view logs

fix: correctly check whether CI is running on release or not

fix: correctly check whether CI is running on release or not #33

Triggered via push September 30, 2024 21:21
@npazosmendeznpazosmendez
pushed 0dfdcc7
master
Status Success
Total duration 3m 51s
Artifacts 1

ci.yaml

on: push
test
14s
test
build
2m 25s
build
deploy
52s
deploy
github_binaries
0s
github_binaries
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. 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
package-artifacts
105 MB