Skip to content
Release

[1.21.3] Fix custom maps not syncing (#1679) #646

Sign in to view logs

[1.21.3] Fix custom maps not syncing (#1679)

[1.21.3] Fix custom maps not syncing (#1679) #646

Triggered via push November 18, 2024 11:49
@sciwhiz12sciwhiz12
pushed 6acd7e1
1.21.x
Status Success
Total duration 4m 55s
Artifacts –

release.yml

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

Annotations

4 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 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/