chore: version bump to 3.0.6 to try another nuget release #458
Annotations
14 warnings
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
|
|
|
|
|
test/unit/LocalGroupProcessorTest.cs#L77
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.
|
test/unit/LocalGroupProcessorTest.cs#L94
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.
|
test/unit/GPOLocalGroupProcessorTest.cs#L209
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.
|
test/unit/GPOLocalGroupProcessorTest.cs#L221
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.
|
test/unit/GPOLocalGroupProcessorTest.cs#L238
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.
|
test/unit/ACLProcessorTest.cs#L553
The variable 'expectedRightName' is assigned but its value is never used
|
test/unit/ACLProcessorTest.cs#L696
The variable 'expectedRightName' is assigned but its value is never used
|
test/unit/ACLProcessorTest.cs#L803
The variable 'expectedRightName' is assigned but its value is never used
|
The logs for this run have expired and are no longer available.
Loading