Skip to content

Update actions/setup-dotnet action to v5 #95

Update actions/setup-dotnet action to v5

Update actions/setup-dotnet action to v5 #95

Triggered via pull request September 6, 2025 19:50
Status Success
Total duration 2m 48s
Artifacts 4

build-test.yaml

on: pull_request
Matrix: .NET Build
Deploy Testing
Deploy Testing
Deploy Production
Deploy Production
Fit to window
Zoom out
Zoom in

Annotations

6 warnings and 1 notice
.NET Build (macOS-latest): Http/samples/Web/Program.cs#L26
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET Build (macOS-latest): Http/samples/Web/Program.cs#L26
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET Build (ubuntu-latest): Http/samples/Web/Program.cs#L26
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET Build (ubuntu-latest): Http/samples/Web/Program.cs#L26
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET Build (windows-latest): Http/samples/Web/Program.cs#L26
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET Build (windows-latest): Http/samples/Web/Program.cs#L26
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET Build (windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Artifacts

Produced during runtime
Name Size Digest
artifacts Expired
1.63 MB
sha256:08bb439c76e5ca2d659f3e675ab0348294bbea46ccec08408022f720d663af9a
test-results-macOS-latest Expired
117 KB
sha256:31202449fdf5008b9bcf05526bff4795b0e8deb1eae5630e0cad863e7d638301
test-results-ubuntu-latest Expired
115 KB
sha256:5777ea9d99b392777bb703a417adcc5998660be69656ea2d54b658f62d43f2a7
test-results-windows-latest Expired
147 KB
sha256:a6ff79eac51c9bdc0fba6ea367cb23b11feadff11bfdc02974a3810b13af99eb