0.28.6.4 #251
publish-hc.yml
on: pull_request
Build and Release
3m 51s
Annotations
11 warnings
|
Build and Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build and Release:
Shared/Pipes/PipeServer.cs#L69
Cannot convert null literal to non-nullable reference type.
|
|
Build and Release:
Shared/Pipes/PipeClient.cs#L65
Cannot convert null literal to non-nullable reference type.
|
|
Build and Release:
Shared/Pipes/PipeServer.cs#L29
Non-nullable event 'ClientMessage' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the event as nullable.
|
|
Build and Release:
Shared/Pipes/PipeServer.cs#L29
Non-nullable event 'Disconnected' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the event as nullable.
|
|
Build and Release:
Shared/Pipes/PipeServer.cs#L29
Non-nullable event 'Connected' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the event as nullable.
|
|
Build and Release:
Shared/Pipes/PipeServer.cs#L33
Nullability of reference types in type of parameter 'sender' of 'void PipeServer.SendMessageQueue(object sender, ElapsedEventArgs e)' doesn't match the target delegate 'ElapsedEventHandler' (possibly because of nullability attributes).
|
|
Build and Release:
Shared/Pipes/PipeClient.cs#L25
Non-nullable event 'ServerMessage' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the event as nullable.
|
|
Build and Release:
Shared/Pipes/PipeClient.cs#L25
Non-nullable event 'Disconnected' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the event as nullable.
|
|
Build and Release:
Shared/Pipes/PipeClient.cs#L25
Non-nullable event 'Connected' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the event as nullable.
|
|
Build and Release:
Shared/Pipes/PipeClient.cs#L29
Nullability of reference types in type of parameter 'sender' of 'void PipeClient.SendMessageQueue(object sender, ElapsedEventArgs e)' doesn't match the target delegate 'ElapsedEventHandler' (possibly because of nullability attributes).
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
HandheldCompanion-0.28.6.251
|
80.2 MB |
sha256:cfc51d009ef31313db1b70357135648e1589b20f3c47c2cf4587ad5b1bc436a4
|
|