Remove .NET Core 3.1 and .NET 5 as supported framework and update sap… #120
michaelvs97
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
17 warnings
|
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, alirezanet/publish-nuget@v3.0.3, actions/create-release@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build:
AspNetCore.ReCaptcha.Tests/TestLogger.cs#L22
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build:
AspNetCore.ReCaptcha.Tests/TestLogger.cs#L22
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build:
AspNetCore.ReCaptcha.Tests/ReCaptchaServiceTests.cs#L71
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
build:
AspNetCore.ReCaptcha.Tests/ReCaptchaServiceTests.cs#L113
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
build:
AspNetCore.ReCaptcha.Tests/ReCaptchaServiceTests.cs#L160
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
build:
AspNetCore.ReCaptcha.Tests/ReCaptchaServiceTests.cs#L204
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
build:
AspNetCore.ReCaptcha.Tests/ReCaptchaServiceTests.cs#L248
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
|
|
build:
Samples/AspNetCore.ReCaptcha.RazorPages/Pages/Error.cshtml.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build:
Samples/AspNetCore.ReCaptcha.Mvc/Models/ErrorViewModel.cs#L5
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build:
AspNetCore.ReCaptcha.Tests/TestLogger.cs#L22
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|