Skip to content

[1.20.x] Fix patch conflicts introduced by #999 (#1057) #346

[1.20.x] Fix patch conflicts introduced by #999 (#1057)

[1.20.x] Fix patch conflicts introduced by #999 (#1057) #346

Triggered via push June 4, 2024 08:12
Status Success
Total duration 7m 46s
Artifacts

release.yml

on: push
release  /  Compute version
4s
release / Compute version
release  /  Build notifications (start)
6s
release / Build notifications (start)
release  /  gradle
7m 11s
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)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: neoforged/action-github-status@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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 / gradle
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: gradle/gradle-build-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
release / Build notifications (end)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: neoforged/action-github-status@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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/