Skip to content

chore: version bump (#170) #154

chore: version bump (#170)

chore: version bump (#170) #154

Re-run triggered October 18, 2024 16:14
Status Failure
Total duration 3m 59s
Artifacts 2

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 14 warnings
nuget
Process completed with exit code 1.
nuget
The following actions uses node12 which is deprecated and will be forced to run on node16: web3j/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
nuget
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, web3j/[email protected], actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
nuget: src/CommonLib/LdapConnectionPool.cs#L22
Field 'LdapConnectionPool._semaphore' is never assigned to, and will always have its default value null
nuget
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
nuget
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=v8.0'. This project may not be fully compatible with your project.
nuget
ProjectReference 'D:\a\SharpHoundCommon\SharpHoundCommon\src\SharpHoundRPC\SharpHoundRPC.csproj' was resolved using '.NETFramework,Version=v4.6.2' instead of the project target framework '.NETCoreApp,Version=v8.0'. This project may not be fully compatible with your project.
nuget: src/CommonLib/LdapConnectionPool.cs#L22
Field 'LdapConnectionPool._semaphore' is never assigned to, and will always have its default value null
nuget: test/unit/UserRightsAssignmentProcessorTest.cs#L81
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.
nuget: test/unit/ComputerSessionProcessorTest.cs#L215
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.
nuget: test/unit/AsyncEnumerableTests.cs#L79
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.
nuget: test/unit/AsyncEnumerableTests.cs#L89
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.
nuget: test/unit/ComputerSessionProcessorTest.cs#L234
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.
nuget: test/unit/Facades/FacadeHelpers.cs#L13
'FormatterServices' is obsolete: 'Formatter-based serialization is obsolete and should not be used.' (https://aka.ms/dotnet-warnings/SYSLIB0050)
nuget: test/unit/LocalGroupProcessorTest.cs#L129
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.

Artifacts

Produced during runtime
Name Size
report
976 KB