Bump version to 1.1.0 #83
hekuAnnotations
12 warnings
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "nuget".
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/
|
|
build-test-and-push
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithReturn.cs#L27
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithWaitAndReturn.cs#L42
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L48
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L59
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithReturn.cs#L27
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithWaitAndReturn.cs#L42
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L48
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L59
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithReturn.cs#L27
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-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithReturn.cs#L27
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)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
nuget
|
16.9 KB |
|