Skip to content

Merge pull request #85 from BloodHoundAD/bump_version #27

Merge pull request #85 from BloodHoundAD/bump_version

Merge pull request #85 from BloodHoundAD/bump_version #27

Triggered via push January 19, 2024 21:37
Status Success
Total duration 1m 25s
Artifacts

publish.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

24 warnings
Build (Debug)
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 (Debug)
.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 (Debug): src/Producers/ComputerFileProducer.cs#L83
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 (Debug): src/Sharphound.cs#L131
The variable 'e' is declared but never used
Build (Debug): src/Runtime/ObjectProcessors.cs#L528
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 (Debug): src/Runtime/ObjectProcessors.cs#L563
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 (Debug): src/Runtime/ObjectProcessors.cs#L665
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 (Debug): src/Runtime/ObjectProcessors.cs#L706
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 (Debug): src/Producers/ComputerFileProducer.cs#L83
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 (Debug): src/Sharphound.cs#L131
The variable 'e' is declared but never used
Build (Debug): src/Runtime/ObjectProcessors.cs#L528
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 (Debug): src/Runtime/ObjectProcessors.cs#L563
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 (Release)
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 (Release)
.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 (Release): src/Sharphound.cs#L131
The variable 'e' is declared but never used
Build (Release): src/Producers/ComputerFileProducer.cs#L83
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 (Release): src/Runtime/ObjectProcessors.cs#L528
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 (Release): src/Runtime/ObjectProcessors.cs#L563
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 (Release): src/Runtime/ObjectProcessors.cs#L665
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 (Release): src/Runtime/ObjectProcessors.cs#L706
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 (Release): src/Sharphound.cs#L131
The variable 'e' is declared but never used
Build (Release): src/Producers/ComputerFileProducer.cs#L83
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 (Release): src/Runtime/ObjectProcessors.cs#L528
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 (Release): src/Runtime/ObjectProcessors.cs#L563
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.