Skip to content

chore(deps): bump actions/setup-dotnet from 5.2.0 to 5.4.0 #20

chore(deps): bump actions/setup-dotnet from 5.2.0 to 5.4.0

chore(deps): bump actions/setup-dotnet from 5.2.0 to 5.4.0 #20

Triggered via pull request June 28, 2026 09:22
Status Success
Total duration 1m 30s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
build-and-test: test/RabstackQuery.Tests/TimeProviderTests.cs#L249
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/TimeProviderTests.cs#L206
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/TimeProviderTests.cs#L185
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/TypeErgonomicsTests.cs#L114
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/CriticalBugFixTests.cs#L336
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/CriticalBugFixTests.cs#L212
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/TypeErgonomicsTests.cs#L53
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/CriticalBugFixTests.cs#L123
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/CriticalBugFixTests.cs#L118
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build-and-test: test/RabstackQuery.Tests/InfiniteQueryObserverTests.cs#L86
The variable 'isFetchingNextPageSeen' is assigned but its value is never used
build-and-test: src/RabstackQuery.DevTools/RestoreOperation.cs#L16
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
build-and-test: src/RabstackQuery.DevTools/RestoreOperation.cs#L16
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.