Skip to content
Triggered via release September 30, 2024 03:14
Status Success
Total duration 47s
Artifacts

publish.yml

on: release
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
Build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3, SethCohen/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build: AutoDuty/IPC/IPCSubscriber.cs#L72
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build: AutoDuty/Windows/LogTab.cs#L33
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: AutoDuty/Helpers/TrustHelper.cs#L118
Dereference of a possibly null reference.
Build: AutoDuty/Helpers/TrustHelper.cs#L119
Dereference of a possibly null reference.
Build: AutoDuty/Helpers/TrustHelper.cs#L120
Dereference of a possibly null reference.
Build: AutoDuty/Helpers/TrustHelper.cs#L121
Dereference of a possibly null reference.
Build: AutoDuty/AutoDuty.cs#L189
Non-nullable field 'PathsDirectory' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build: AutoDuty/AutoDuty.cs#L189
Non-nullable field 'AssemblyFileInfo' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build: AutoDuty/AutoDuty.cs#L189
Non-nullable field 'ConfigFile' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build: AutoDuty/AutoDuty.cs#L189
Non-nullable property 'Configuration' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.