Bug: dotnet-coverage v17.9.0 broke our CI-pipeline

[lindeberg]

Our GitHub Actions Workflow containing these steps started failing with Error: Process completed with exit code 150. now that dotnet-coverage 17.9.0 got released.

...
runs-on: [self-hosted, linux]
...
 - name: Setup .NET
   uses: actions/setup-dotnet@v3
   with:
     dotnet-version: 7.0.x <--(happens with 6.0.x too)

 - name: Add dotnet-tools to PATH
    run: echo "/home/runner/.dotnet/tools" >> "$GITHUB_PATH"

  - name: Merge coverage reports
    run: |
      dotnet tool install --global dotnet-coverage
      cd ${{ env.TEST_RESULTS_PATH }}
      dotnet-coverage merge --output coverage-merged.xml --output-format cobertura --recursive coverage.cobertura.xml

was successful with 17.8.6:

We are using this with a dozen workflows and would prefer not to specify the old version in all of them.

[mhsFlairs]

+1

[iamkinetic]

We have the same problem with our GitLab CI pipelines.

[olegpuz]

same here. pls revert latest version to 17.8.6, because current one is broken!

[jakubch1]

I am working on fix. As workaround you can use previous version or set env variable DOTNET_ROLL_FORWARD = Major

[mickvdv]

Workaround is adding --version 17.8.6 to the dotnet tool install command:

dotnet tool install --global dotnet-coverage --version 17.8.6

[jakubch1]

We have unlisted 17.9.0 version.

[lindeberg]

@jakubch1 Not sure how unlisting works, but pipeline is still fetching 17.9.

[jakubch1]

17.9.1 with fix was released. Thanks for reporting this

[minoseah629]

@jakubch1 are there any release notes to this update from 17.8.6 to 17.9.1. other microsoft nuget package has some level of release notes.