Skip to content

v1.2.33-pre

v1.2.33-pre #60

Triggered via release July 19, 2024 12:29
@idchronoidchrono
published v1.2.33-pre
Status Success
Total duration 17m 40s
Artifacts 1
Build, Test & Publish to NuGet
17m 31s
Build, Test & Publish to NuGet
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "test-results". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
Build, Test & Publish to NuGet
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, docker/login-action@v2, actions/setup-dotnet@v3, nuget/setup-nuget@v1, actions/upload-artifact@v3, docker/setup-buildx-action@v2, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build, Test & Publish to NuGet
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build, Test & Publish to NuGet
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, Test & Publish to NuGet
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.

Artifacts

Produced during runtime
Name Size
test-results Expired
987 KB