Skip to content
Release

Trigger build #2

Sign in to view logs

Trigger build

Trigger build #2

Triggered via push August 24, 2024 07:26
@RaycomsRaycoms
pushed aeaa9b1
version/latest
Status Failure
Total duration 2m 12s
Artifacts –

release.yml

on: push
release  /  ...  /  compute-version
4s
release / compute-version / compute-version
release  /  🔴 Build notifications (start)
3s
release / 🔴 Build notifications (start)
release  /  gradle
1m 40s
release / gradle
release  /  Build notifications (end)
5s
release / Build notifications (end)
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
release / gradle
Process completed with exit code 1.
release / 🔴 Build notifications (start)
The following actions uses node12 which is deprecated and will be forced to run on node16: neoforged/action-github-status@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
release / 🔴 Build notifications (start)
The following actions use a deprecated Node.js version and will be forced to run on node20: neoforged/action-github-status@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
release / Build notifications (end)
The following actions uses node12 which is deprecated and will be forced to run on node16: neoforged/action-github-status@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
release / Build notifications (end)
The following actions use a deprecated Node.js version and will be forced to run on node20: neoforged/action-github-status@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/