Skip to content
CI

Fix/generate gh release directly (#627) #3179

Sign in to view logs

Fix/generate gh release directly (#627)

Fix/generate gh release directly (#627) #3179

Triggered via push October 24, 2024 15:41
@TheMaskedTurtleTheMaskedTurtle
pushed 2930ff1
main
Status Success
Total duration 3m 36s
Artifacts –

build.yml

on: push
Check licenses headers
27s
Check licenses headers
build
3m 26s
build
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Check licenses headers
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.
Check licenses headers
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check licenses headers
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/checkout@v2, 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 uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/