Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Possible null reference argument for parameter 'interactionId' in 'Task IClient.SendInteractionResponseAsync(string interactionId, string interactionToken, string responseJson, CancellationToken cancellation = default(CancellationToken))'.

Converting null literal or possible null value to non-nullable type.

Non-nullable field '_containerBuilder' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Converting null literal or possible null value to non-nullable type.

Possible null reference argument for parameter 's' in 'long long.Parse(string s)'.

Possible null reference argument for parameter 'token' in 'AppConfiguration.AppConfiguration(string token, char botPrefix = '!')'.

Non-nullable property 'Response' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Non-nullable property 'Response' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Non-nullable field '_clientConfiguration' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.