chore(deps): update codecov/codecov-action action to v4 - autoclosed #44
Annotations
24 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-dotnet@v3, actions/upload-artifact@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L51
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L58
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L65
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L72
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L97
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L88
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L89
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L79
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L90
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L80
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L51
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L58
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L65
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L72
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L79
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L80
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L81
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L88
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L89
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)
|
|
tests/Finbuckle.MultiTenant.MongoFramework.Tests/MongoTenantStoreShould.cs#L90
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)
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "artifact".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
This job succeeded
Loading