Skip to content

Merge pull request #69 from BloodHoundAD/publish_github_nuget #470

Merge pull request #69 from BloodHoundAD/publish_github_nuget

Merge pull request #69 from BloodHoundAD/publish_github_nuget #470

Triggered via push August 16, 2023 18:14
Status Success
Total duration 10m 23s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
build
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/
build
ProjectReference 'D:\a\SharpHoundCommon\SharpHoundCommon\src\CommonLib\SharpHoundCommonLib.csproj' was resolved using '.NETFramework,Version=v4.6.2' instead of the project target framework '.NETCoreApp,Version=v5.0'. This project may not be fully compatible with your project.
build
.NET 5.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
build
ProjectReference 'D:\a\SharpHoundCommon\SharpHoundCommon\src\CommonLib\SharpHoundCommonLib.csproj' was resolved using '.NETFramework,Version=v4.6.2' instead of the project target framework '.NETCoreApp,Version=v5.0'. This project may not be fully compatible with your project.
build: test/unit/ACLProcessorTest.cs#L553
The variable 'expectedRightName' is assigned but its value is never used
build: test/unit/ACLProcessorTest.cs#L696
The variable 'expectedRightName' is assigned but its value is never used
build: test/unit/ACLProcessorTest.cs#L803
The variable 'expectedRightName' is assigned but its value is never used
build: test/unit/ACLProcessorTest.cs#L877
The variable 'expectedRightName' is assigned but its value is never used
build: test/unit/ComputerSessionProcessorTest.cs#L204
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.
build: test/unit/ComputerSessionProcessorTest.cs#L220
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.
build: test/unit/GPOLocalGroupProcessorTest.cs#L208
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.
build: test/unit/GPOLocalGroupProcessorTest.cs#L220
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.
build: test/unit/GPOLocalGroupProcessorTest.cs#L237
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.