-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to select version of coverage-reporter #170
Comments
@ogenstad Agree this would be a very helpful option. Have added it to our backlog for consideration. Thanks. |
Is there any update on this? After https://github.com/coverallsapp/coverage-reporter/releases/tag/v0.6.8 was released our pipelines have started to fail with:
|
@ogenstad sorry for the delay and thank you for opening coverallsapp/coverage-reporter#119. This goes in the hopper this week, along with the same ability in our other CI extension (CircleCI Orb). I'll post updates here, and here. |
@ogenstad wanted to let you know that we cut a new release of the Coveralls GitHub Action ( When you get a chance to use it, please let us know how it works for you. For those waiting on the same ability in our CircleCI Orb, that is WIP. Please give us another week or so. I'm going to close this. Please re-open if any issues. |
Yesterday our CI started to see failures after the release of coverage-reporter v0.3.8 as reported in that repo here, looking through the repo it seems that v0.3.7 resulted in failures of other pipelines
By default for at least Windows and Mac the v2 version of this action downloads either https://github.com/coverallsapp/coverage-reporter/releases/latest/download/coveralls-linux.tar.gz or https://github.com/coverallsapp/coverage-reporter/releases/latest/download/coveralls-windows.zip.
It would be nice if it was possible to pin the version of coverage-reporter that this action would use to ensure that the pipelines can continue to work if bugs are introduced to future versions of coverage-reporter.
The text was updated successfully, but these errors were encountered: