Skip to content
Release

Fix synchronisation for Eclipse/VSCode (#174) #171

Sign in to view logs

Fix synchronisation for Eclipse/VSCode (#174)

Fix synchronisation for Eclipse/VSCode (#174) #171

Triggered via push October 14, 2024 08:49
@Technici4nTechnici4n
pushed b0eff18
main
Status Success
Total duration 5m 34s
Artifacts –

release.yml

on: push
release  /  Compute version
8s
release / Compute version
release  /  Build notifications (start)
5s
release / Build notifications (start)
release  /  gradle
4m 57s
release / gradle
release  /  Build notifications (end)
4s
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/