Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v1. 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/

'ISystemClock' is obsolete: 'Use TimeProvider instead.'

The variable 'e' is declared but never used

The variable 'b' is assigned but its value is never used

The variable 'a' is assigned but its value is never used

The variable 'e' is declared but never used

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.

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.

Possible unintended reference comparison; to get a value comparison, cast the left hand side to type 'string'

Possible unintended reference comparison; to get a value comparison, cast the left hand side to type 'string'

'ISystemClock' is obsolete: 'Use TimeProvider instead.'

The variable 'e' is declared but never used

The variable 'b' is assigned but its value is never used

The variable 'a' is assigned but its value is never used

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.

The variable 'e' is declared but never used

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.

Possible unintended reference comparison; to get a value comparison, cast the left hand side to type 'string'