Skip to content

fix deployment path

fix deployment path #1

Triggered via push September 18, 2024 13:01
Status Failure
Total duration 6m 51s
Artifacts
build-and-release-linux
43s
build-and-release-linux
build-and-release-windows
6m 37s
build-and-release-windows
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
build-and-release-linux
Process completed with exit code 100.
build-and-release-linux
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, subosito/flutter-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-release-linux
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, subosito/flutter-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-release-windows
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, subosito/flutter-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-release-windows
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, subosito/flutter-action@v1, softprops/action-gh-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/