Skip to content

0.7.0

0.7.0 #7

Triggered via release October 11, 2024 17:28
@eBaezaeBaeza
published 0.7.0
Status Success
Total duration 1m 25s
Artifacts 1

release.yml

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

Annotations

11 warnings
build (Release)
The following actions use a deprecated Node.js version and will be forced to run on node20: microsoft/[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 (Release): Resource Manager/ExtractDialog.xaml.cs#L7
The using directive for 'System.IO' appeared previously in this namespace
build (Release): Resource Manager/Classes/Ddt/Ddt.cs#L307
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build (Release): Resource Manager/Classes/Webp/WebPWrapper.cs#L1162
The result of the expression is always 'false' since a value of type 'nint' is never equal to 'null' of type 'nint?'
build (Release): Resource Manager/Classes/Webp/WebPWrapper.cs#L1166
The result of the expression is always 'false' since a value of type 'nint' is never equal to 'null' of type 'nint?'
build (Release): Resource Manager/Classes/Webp/WebPWrapper.cs#L1189
The result of the expression is always 'false' since a value of type 'nint' is never equal to 'null' of type 'nint?'
build (Release): Resource Manager/Classes/Webp/WebPWrapper.cs#L1193
The result of the expression is always 'false' since a value of type 'nint' is never equal to 'null' of type 'nint?'
build (Release): Resource Manager/Classes/Webp/WebPWrapper.cs#L1216
The result of the expression is always 'false' since a value of type 'nint' is never equal to 'null' of type 'nint?'
build (Release): Resource Manager/Classes/Webp/WebPWrapper.cs#L1220
The result of the expression is always 'false' since a value of type 'nint' is never equal to 'null' of type 'nint?'
build (Release): Resource Manager/MainWindow.xaml.cs#L1054
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): Resource Manager/CompareWindow.xaml.cs#L402
The variable 'ex' is declared but never used

Artifacts

Produced during runtime
Name Size
ResourceManager
9.99 MB