Skip to content
Release

Fix publishing #39

Sign in to view logs

Fix publishing

Fix publishing #39

Triggered via push July 25, 2024 09:16
@MatyrobbrtMatyrobbrt
pushed 5c322ce
main
Status Success
Total duration 7m 49s
Artifacts –

release.yml

on: push
release  /  Compute version
3s
release / Compute version
release  /  Build notifications (start)
3s
release / Build notifications (start)
release  /  gradle
7m 16s
release / gradle
release  /  Build notifications (end)
5s
release / Build notifications (end)
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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 uses Node.js version which is deprecated 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 / gradle
The following actions uses Node.js version which is deprecated and will be forced to run on node20: gradle/gradle-build-action@v2. 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 uses Node.js version which is deprecated 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/