Skip to content

Fixed supported frameworks in project description and readme #3497

Fixed supported frameworks in project description and readme

Fixed supported frameworks in project description and readme #3497

Triggered via pull request December 19, 2024 01:31
Status Success
Total duration 6m 17s
Artifacts 1

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

25 warnings
Compat
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test: src/Examples/Program.cs#L12
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 and test: src/Examples/V2/ThinEventWebhookHandler.cs#L31
Possible null reference assignment.
Build and test: src/Examples/V2/ThinEventWebhookHandler.cs#L26
Non-nullable field '_webhookSecret' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build and test: src/Examples/ExampleTemplate.cs#L24
The variable 'apiKey' is assigned but its value is never used
Build and test: src/Examples/ExampleTemplate.cs#L22
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 and test: src/Examples/Program.cs#L12
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 and test: src/Examples/ExampleTemplate.cs#L24
The variable 'apiKey' is assigned but its value is never used
Build and test: src/Examples/ExampleTemplate.cs#L22
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 and test
.NET Core 2.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
Build and test
.NET Core 3.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
Build and test
.NET 5.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
Build and test: src/Examples/Program.cs#L12
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 and test: src/Examples/ExampleTemplate.cs#L24
The variable 'apiKey' is assigned but its value is never used
Build and test: src/Examples/ExampleTemplate.cs#L22
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 and test: src/Examples/Program.cs#L12
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 and test: src/Examples/ExampleTemplate.cs#L24
The variable 'apiKey' is assigned but its value is never used
Build and test: src/Examples/ExampleTemplate.cs#L22
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 and test: src/Examples/V2/ThinEventWebhookHandler.cs#L31
Possible null reference assignment.
Build and test: src/Examples/V2/ThinEventWebhookHandler.cs#L26
Non-nullable field '_webhookSecret' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Artifacts

Produced during runtime
Name Size
nuget
10.6 MB