Skip to content

Update version number #50

Update version number

Update version number #50

Triggered via push October 11, 2023 23:32
Status Success
Total duration 2m 18s
Artifacts

ci.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

39 warnings
build (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, simon-k/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L45
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L59
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L59
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L70
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L121
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L121
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L131
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L143
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L143
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L156
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (ubuntu-latest)
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 (ubuntu-latest)
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 (macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, simon-k/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (macos-latest)
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 (macos-latest)
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 (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L59
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L59
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L121
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L121
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L70
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L143
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L143
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L156
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L45
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (macos-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L131
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
build (windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, simon-k/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (windows-latest): tests/Toimik.WarcProtocol.Tests/RequestRecordTest.cs#L95
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/RequestRecordTest.cs#L112
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/ResponseRecordTest.cs#L90
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/ResponseRecordTest.cs#L107
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L45
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L59
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L59
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L121
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L121
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest): tests/Toimik.WarcProtocol.Tests/WarcParserTest.cs#L70
Test methods should not call ConfigureAwait(), as it may bypass parallelization limits.
build (windows-latest)
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 (windows-latest)
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/