dev - #133

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Type 'WinFormsClipboard' can be sealed because it has no subtypes in its containing assembly and is not externally visible (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1852)

Type 'SettingsProvider' can be sealed because it has no subtypes in its containing assembly and is not externally visible (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1852)

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.