Skip to content

migration to dotnet-isolated #2

migration to dotnet-isolated

migration to dotnet-isolated #2

Triggered via push November 19, 2024 11:19
Status Success
Total duration 3m 13s
Artifacts
build-and-deploy
3m 0s
build-and-deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build-and-deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@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-deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@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-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.