Config cleanup, part 2 (#178) #105

Sign in to view logs

Triggered via push July 10, 2024 22:36

Technici4n

main

Status Success

Total duration 4m 52s

Artifacts –

release.yml

on: push

release / Compute version

release / Build notifications (start)

release / gradle

release / Build notifications (end)

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/